Re: seg fault in contrib/bloom

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: seg fault in contrib/bloom
Date: 2016-05-17 21:40:56
Message-ID: CAMkU=1yyiW27bjepZPoSv91+mYQGKhHshS-gnsgYcBdM03NxLw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 17, 2016 at 2:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
>
> I pushed a patch that should fix this, but without having tried to
> reproduce the problem locally; so possibly I guessed wrong as to
> what is causing it. Please test.

That fixed it.

Cheers,

Jeff

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Flower 2016-05-17 21:47:24 Re: Reviewing freeze map code
Previous Message Vik Fearing 2016-05-17 21:34:38 Re: Reviewing freeze map code