From: | Peter Bex <peter(at)more-magic(dot)net> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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: | 2019-09-16 11:32:57 |
Message-ID: | 20190916113257.GP754@scully.more-magic.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Thu, Sep 05, 2019 at 07:20:14PM -0400, Alvaro Herrera wrote:
> So does this proposal fix the problem that David was describing earlier?
> If it does, Tom, would you like to get this finalized and pushed?
>
> I've bcc'ed someone who might be interested in chiming in and/or helping
> out. Please look here:
> https://postgr.es/m/153683552113.22350.18441286362867559841@wrigleys.postgresql.org
Hi all,
I was the one who originally reported the issue on IRC (Alvarro BCCed me).
It took me a while to find the time to set up a VM with Postgres patched
and unpatched. And I had to figure out which query it was again which
triggered the issue (thank god that Firefox still had my explain pastes
in its history).
But I'm happy to report that the patch actually affects the real life
query in a positive way; it's indeed much faster again after applying
the patch!
Will this make it into Postgres 12?
Cheers,
Peter
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-09-16 13:54:55 | Re: BUG #16007: Regarding patch for BUG #3995: pqSocketCheck doesn't return |
Previous Message | Kiran Khatke | 2019-09-16 06:53:41 | Re: BUG #16007: Regarding patch for BUG #3995: pqSocketCheck doesn't return |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2019-09-16 12:28:43 | Re: range test for hash index? |
Previous Message | Peter Eisentraut | 2019-09-16 11:14:21 | ecpglib major version changed |