Sorry to pester, but I’m not sure how bugs like this are tracked over longer periods of time. The discussion around
possiblefixes for this went above my pay grade, and I’m wondering whether a fix was ever released. If not, is there any
wayfor me to know when it does get fixed other than reviewing release notes?
> On Jul 19, 2016, at 9:18 PM, Tomas Vondra <tomas.vondra@2ndquadrant.com> wrote:
>
> On 07/19/2016 06:22 PM, Tomas Vondra wrote:
>>
>> I don't expect to have much time to work on this in the next few weeks,
>> so if anyone wants to grab this and make it a proper patch, be my guest.
>
> Meh, who am I kidding. I've spent a bit more time hacking on this anyway. Attached is v3, fixing various thinkos and
optimizations,checks in the code and especially docs explaining the main ideas. It's far from perfect but much better
thanthe previous two versions.
>
> And it actually performs even better than the previous versions (about 2x faster on the 50k case).
>
> regards
>
> --
> Tomas Vondra http://www.2ndQuadrant.com
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
> <slab-reorder-buffer-v3.patch>
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
