Re: BUG #14158: PostgreSQL 9.6 bloom don't support unlogged table?

From: Hao Lee <mixtrue(at)gmail(dot)com>
To: digoal(at)126(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14158: PostgreSQL 9.6 bloom don't support unlogged table?
Date: 2016-05-25 12:24:00
Message-ID: CAGoxFiFaNgR8_km2ae52sevZbx0xck6G6wpeZFXwmADG5eZ4ow@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

In bool\blinsert.c, the function "blbuildempty" the if test failed. And, in
catlog\index.c line 2037, after creating the index file, then to build
empty index file. but we got the "one" block number of the relation, that
lead the if test failed.

On Wed, May 25, 2016 at 5:54 PM, <digoal(at)126(dot)com> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 14158
> Logged by: Zhou Digoal
> Email address: digoal(at)126(dot)com
> PostgreSQL version: 9.6beta1
> Operating system: CentOS 6.x x64
> Description:
>
> master=# create extension bloom;
> CREATE EXTENSION ^
> master=# create unlogged table tbl12(id int);
> CREATE TABLE
>
> master=# \set VERBOSITY verbose
> master=# create index idx1 on tbl12 using bloom (id);
> ERROR: XX000: index "idx1" already contains data
> LOCATION: blbuildempty, blinsert.c:164
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeff Janes 2016-05-25 12:45:19 Re: [BUGS] BUG #14155: bloom index error with unlogged table
Previous Message digoal 2016-05-25 11:51:53 BUG #14159: PostgreSQL 9.6 parallel scan consume very high mutex lock