| From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Planner Row Estimate with Function |
| Date: | 2009-12-29 18:39:40 |
| Message-ID: | hhdict$1dg$1@ger.gmane.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Michael Fork wrote on 29.12.2009 18:08:
> 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?
You can add the ROWS nnn option to your create statement to give the planner a hint about the number of rows:
http://www.postgresql.org/docs/current/static/sql-createfunction.html
Check out the /ROWS result_rows/ part.
Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua Tolley | 2009-12-29 18:57:40 | Re: Comparing 2 databases |
| Previous Message | Pavel Stehule | 2009-12-29 18:16:10 | Re: Planner Row Estimate with Function |