On 04/05/2014 08:08 PM, Tom Lane wrote:
I tried the test case given in http://www.postgresql.org/message-id/dafad644f268ce1503e1b8b682aae38a.squir...@webmail.xs4all.nl on HEAD. It asserted here: ... #5 0x000000000046b92b in createPostingTree (index=0x7f1348ae31e0, items=0x7f13343bb048, nitems=272428, buildStats=0x7fff1d835670) at gindatapage.c:1739
Yep, that's a clear violation of the no-pallocs-in-critical-section rule. Thanks, fixed.
I'm surprised none of the existing regression tests caught that. Apparently none of them create a GIN index with enough duplicate keys that it would create a posting tree. I added one.
- Heikki -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
