| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David Johnston" <polobo(at)yahoo(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: A Better Way? (Multi-Left Join Lookup) |
| Date: | 2012-07-21 21:47:37 |
| Message-ID: | 29022.1342907257@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I wrote:
> "David Johnston" <polobo(at)yahoo(dot)com> writes:
>> So,
>> EXPLAIN SELECT function_call(...) -- yields a planner expectation of 1 row
>> [Whereas]
>> EXPLAIN SELECT * FROM function_call(...) -- yields a planner expectation of
>> "result_rows" which defaults to 1000
> Hm ...
>> Was this an intentional design decision to override the result_rows estimate
>> of the function if it is used in the select list?
> Not so much an intentional decision as just that nobody ever did
> anything about it.
I've now done something about that for 9.2. I'm loath to back-patch it
into any already-stable releases, though, for fear of destabilizing
plan choices that production applications might be relying on.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johnston | 2012-07-22 00:48:07 | Re: A Better Way? (Multi-Left Join Lookup) |
| Previous Message | Tom Lane | 2012-07-21 17:36:15 | Re: A Better Way? (Multi-Left Join Lookup) |