From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New design for FK-based join selectivity estimation |
Date: | 2016-06-13 19:51:16 |
Message-ID: | 1888.1465847476@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> On 13 June 2016 at 19:16, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Another point here is that I'm now unconvinced that restricting the logic
>> to consider only multi-column fkeys is really what we want. It looks to
>> me like the code can also improve estimates in the case where there are
>> multiple single-column FKs linking to the same target relation. That
>> might not be too common for two-table queries, but I bet it happens a
>> lot in three-or-more-table queries.
> Is it realistic that we consider that at this point? Certainly not for
> myself, at least.
It's pretty much built into the redesign I proposed, or so I thought.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-06-13 19:52:59 | Re: ERROR: ORDER/GROUP BY expression not found in targetlist |
Previous Message | Tom Lane | 2016-06-13 19:42:49 | Re: ERROR: ORDER/GROUP BY expression not found in targetlist |