Michael Fork <[email protected]> writes:
> I have an index scan on a custom function that is returning a wildly
> incorrect row estimate that is throwing off the rest of the query planning.
> The result of the function is roughly unique - there are a handful with
> multiple entries - but the planner is estimating 227,745 rows. I re-ran
> ANALYZE on the table and the results did not change. Any suggestions on how
> to get more accurate planner result?
What PG version is this exactly?
Also, what happened to the type='CREDIT' condition in your query? Is
that a partial index?
regards, tom lane
--
Sent via pgsql-general mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
