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