From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: seg fault in contrib/bloom |
Date: | 2016-05-17 18:23:14 |
Message-ID: | 1550.1463509394@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> I'm getting seg faults on contrib/bloom when updating a tuple which
> was found via a bloom index.
> It does not happen on every update, but it does happen within a few
> seconds of run time, so it is readily reproducible. The test harness
> is a bit of a mess, I'll try to clean it up and post it if no one
> spots the bug soon via looking at the stack trace below.
> Obviously scan->opaque is null, but I don't know why it is null and
> whether blendscan is obliged to deal with nulls, or if index_endscan
> is obliged not to send them.
I'm guessing there is a code path that can get from blbeginscan to
blendscan without going through blrescan. I'm not sure why it'd
only happen sometimes, though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2016-05-17 19:09:47 | pgsql: Allocate all page images at once in generic wal interface |
Previous Message | David G. Johnston | 2016-05-17 17:56:35 | Re: Parameters don't work in FETCH NEXT clause? |