Re: BUG #14155: bloom index error with unlogged table

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: digoal(at)126(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14155: bloom index error with unlogged table
Date: 2016-05-25 01:04:53
Message-ID: CAB7nPqR2CVyxLHc5um64vudg6Ncj=r3XdbKz4vsZR_61+A=sDA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Tue, May 24, 2016 at 5:08 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> digoal(at)126(dot)com writes:
>> postgres=# create unlogged table u_tbl (id int);
>> CREATE TABLE
>> postgres=# create index idx_u_tbl on u_tbl using bloom (id);
>> ERROR: index "idx_u_tbl" already contains data
>
> 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?
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-05-25 01:11:05 Re: BUG #14155: bloom index error with unlogged table
Previous Message David G. Johnston 2016-05-25 00:27:04 Re: [BUGS] BUG #14155: bloom index error with unlogged table

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-05-25 01:09:52 Re: Parallel safety tagging of extension functions
Previous Message Joe Conway 2016-05-25 01:04:36 RLS related docs