On Fri, Dec 2, 2016 at 10:04 PM, Amit Kapila <amit.kapil...@gmail.com> wrote:
>> Here we shouldn't be accessing meta page after releasing the lock as
>> concurrent activity can change these values. This can be fixed by
>> storing these values in local variables before releasing the lock and
>> passing local variables in hashbucketcleanup(). I will send patch
> Please find attached patch to fix above code.
Committed. I don't know either whether this will fix things for
Andreas, but it's certainly a bug fix in its own right.
The Enterprise PostgreSQL Company
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: