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
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-general pgsql-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


Browse pgsql-general by date

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

Browse pgsql-hackers by date

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