Re: New design for FK-based join selectivity estimation
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2016-06-13T19:51:16Z
Lists: pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes: > On 13 June 2016 at 19:16, Tom Lane <tgl@sss.pgh.pa.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
Commits
-
Fix FK-based join selectivity estimation for semi/antijoins.
- f4f195d15c7c 9.6.2 landed
- 7fa93eec4e0c 10.0 landed
-
Restore foreign-key-aware estimation of join relation sizes.
- 100340e2dcd0 9.6.0 cited