Re: BUG #14155: bloom index error with unlogged table - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #14155: bloom index error with unlogged table
Date
Msg-id CAB7nPqSkP6mpga9xkVPd3AcKqm7h6+2JVBOHozT7dRBSpQS3UQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14155: bloom index error with unlogged table  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Tue, May 24, 2016 at 6:11 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Michael Paquier <michael.paquier@gmail.com> writes:
>>> Yeah, it looks like nobody ever tested bloom's unlogged-index support;
>>> it doesn't work or even come very close to working.  Will fix, thanks
>>> for the report!
>
>> To be honest, I began hacking around that to address the issue, though
>> I don't have yet something to post... So I guess that there is nothing
>> I need to do? Or do you need a patch?
>
> Nah, I just pushed something ... but if you'd like to go over the
> documentation thread David was complaining about and produce a cleaned-up
> docs patch, that would be pretty helpful.

OK. I'll get a look at this thread and see how the documentation can
be improved by replying there, though there is already a patch I
see...
--
Michael

pgsql-bugs by date:

Previous
From: David Gould
Date:
Subject: Re: BUG #14168: ALTER TABLE SET LOGGED failing
Next
From: Michael Meskes
Date:
Subject: Re: BUG #14167: ecpg parser cann't ignore code in #ifdef ?