On 04.05.2017 22:16, Tom Lane wrote:
Nikita Glukhov <n.glu...@postgrespro.ru> writes:
In gistrescan() IndexScanDesc.xs_hitup is not reset after MemoryContextReset()
so->queueCxt in which xs_hitup was allocated, then getNextNearest() tries to
dangling xs_hitup, which results in the reuse of this pointer and the
Right. I already did something about this, about an hour ago --- a
bit differently from your patch, but same idea.
regards, tom lane
Sorry that I'm not monitoring pgsql-bugs.
It might be interesting that I found this bug back in July 2016 when I
was experimenting with my KNN-btree implementation, but I failed to report
it because I could reproduce it only manually by a calling in a loop
gistrescan() and gistgettuple().
The Russian Postgres Company
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: