Re: Index trouble with 8.3b4

From: Hannes Dorbath <light(at)theendofthetunnel(dot)de>
To: Gregory Stark <stark(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Index trouble with 8.3b4
Date: 2008-01-13 18:50:51
Message-ID: 478A5D8B.1060601@theendofthetunnel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Gregory Stark wrote:
> "Gregory Stark" <stark(at)enterprisedb(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Guillaume Smet 2008-01-13 19:02:34 Re: Index trouble with 8.3b4
Previous Message Tom Lane 2008-01-13 17:33:28 Re: How to safely compare transaction id?

Browse pgsql-hackers by date

  From Date Subject
Next Message Guillaume Smet 2008-01-13 19:02:34 Re: Index trouble with 8.3b4
Previous Message Magnus Hagander 2008-01-13 18:09:45 Re: Make pg_dump suppress COMMENT ON SCHEMA public ?