Re: Index trouble with 8.3b4 - Mailing list pgsql-hackers

From Hannes Dorbath
Subject Re: Index trouble with 8.3b4
Date
Msg-id 478A5D8B.1060601@theendofthetunnel.de
Whole thread Raw
In response to Re: Index trouble with 8.3b4  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Index trouble with 8.3b4  ("Guillaume Smet" <guillaume.smet@gmail.com>)
List pgsql-hackers
Gregory Stark wrote:
> "Gregory Stark" <stark@enterprisedb.com> writes:
> 
>> On the other hand we can't just ignore all vacuums because someone could issue
>> a manual vacuum inside a transaction (I think?). 
> 
> Doh, ignore this. sigh.


I started from scratch to put up a test case. I cannot trigger "ERROR: 
item pointer (0,1) already exists" again as the deadlock issue reported 
by Gregory Stark hit me every time. Is this fixed in RC1? Can I retry 
with that?

Only good news is that I think I found the CLUSTER issue:

It was no GIST index I created, I accidentally created a BTREE index:
http://theendofthetunnel.de/cluster.txt

If it does help anything, the data and setup:

8.3-b4 build from source

./configure --prefix=/usr/local --enable-thread-safety --with-perl 
--with-openssl --with-libxml --with-libxslt

initdb line:
initdb -D /data/pgsql --locale='de_DE.utf8' --lc-collate='C'

Only listen_address and pg_hba.conf was touched.

Please get the -Fc dump (37MB) from:

http://theendofthetunnel.de/dump.bin
http://theendofthetunnel.de/glob.sql


-- 
Best regards,
Hannes Dorbath


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Make pg_dump suppress COMMENT ON SCHEMA public ?
Next
From: "Guillaume Smet"
Date:
Subject: Re: Index trouble with 8.3b4