Skip site navigation (1) Skip section navigation (2)

Re: Index trouble with 8.3b4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Hannes Dorbath <light(at)theendofthetunnel(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Index trouble with 8.3b4
Date: 2008-01-07 02:22:09
Message-ID: 1730.1199672529@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
Hannes Dorbath <light(at)theendofthetunnel(dot)de> writes:
> hannes=> CREATE INDEX CONCURRENTLY "ts_fts_tsv" ON "public"."fts" USING gin ("tsv");
> ERROR: item pointer (0,1) alreadt exists

> I was able to reproduce that error a few times, but not always. It seems 
>   it only happens with CONCURRENTLY.

> After creating a GIST index instead of GIN I tried to cluster on that:

> hannes=> CLUSTER fts USING ts_fts_tsv;
> ERROR:  could not create unique index "pk_fts"
> DETAIL:  Table contains duplicated values.
> So duplicate values in my PK column?

I didn't have any luck reproducing either of these behaviors --- maybe
it's data-dependent.  Can you extract a test case?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: ITAGAKI TakahiroDate: 2008-01-07 02:34:12
Subject: Random plan selection in DBT-3
Previous:From: Tom LaneDate: 2008-01-07 01:20:10
Subject: Re: OUTER JOIN performance regression remains in 8.3beta4

pgsql-general by date

Next:From: Hiroshi SaitoDate: 2008-01-07 02:34:39
Subject: Re: Insert returning Npgsql
Previous:From: ClodoaldoDate: 2008-01-06 19:46:33
Subject: Re: Performance problem. Could it be related to 8.3-beta4?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group