From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [COMMITTERS] pgsql: Collect and use multi-column dependency stats |
Date: | 2017-04-05 22:48:57 |
Message-ID: | 4188.1491432537@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> Collect and use multi-column dependency stats
The buildfarm is unhappy about the fact that this changed the API
for clauselist_selectivity(). I am not convinced that that change
was a good idea, so before telling FDW authors that they need to
change their code, I'd like to hear a defense of the API change.
Why not just use the existing varRelid parameter for that? Why
is there an assumption that only one rel's extended stats will
ever be of interest? This function does get used for join clauses.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2017-04-05 23:20:36 | Re: [COMMITTERS] pgsql: Collect and use multi-column dependency stats |
Previous Message | Simon Riggs | 2017-04-05 22:24:15 | pgsql: Reduce lock level for CREATE STATISTICS |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2017-04-05 22:50:39 | Re: GUC for cleanup indexes threshold. |
Previous Message | Michael Paquier | 2017-04-05 22:48:01 | Re: Rewriting the test of pg_upgrade as a TAP test |