From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Marko Tiikkaja <marko(at)joh(dot)to>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #15383: Join Filter cost estimation problem in 10.5 |
Date: | 2020-02-27 19:24:55 |
Message-ID: | 20200227192455.GA1788@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On 2019-Nov-30, Tom Lane wrote:
> Or, since I think we're out of the realm of what would be sane to
> back-patch anyway, maybe it's time to take two steps back and try
> to find a real, non-stopgap solution. As I said upthread, I think
> the core problem here is failure to distinguish quals associated with
> the uniqueness condition from additional "filter" quals that have to
> be checked anyway. I wonder how hard that is to fix.
So does anyone have a way to move this forward? David, any input on
this?
Thanks
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Semanchuk | 2020-02-27 21:13:17 | Re: BUG #16279: Permissions doc incorrect for pg_buffercache |
Previous Message | Дмитрий Вилькер | 2020-02-27 18:27:23 | Postgres does not use index with IN |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2020-02-27 19:31:52 | Re: [GsoC] Read/write transaction-level routing in Odyssey Project Idea |
Previous Message | koschasialis | 2020-02-27 19:23:24 | Re: [GsoC] Read/write transaction-level routing in Odyssey Project Idea |