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

Re: Index trouble with 8.3b4

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Hannes Dorbath" <light(at)theendofthetunnel(dot)de>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Index trouble with 8.3b4
Date: 2008-01-07 14:46:19
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> 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.
> I didn't have any luck reproducing either of these behaviors --- maybe
> it's data-dependent.  Can you extract a test case?

I the GIN problem kicks in with the "posting tree" representation. That would
require more than about 85 records with the same matching lexeme-key.

  Gregory Stark
  Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training!

In response to

pgsql-hackers by date

Next:From: Usama DarDate: 2008-01-07 14:49:47
Subject: Re: Tuning Postgresql on Windows XP Pro 32 bit
Previous:From: Csaba NagyDate: 2008-01-07 13:32:03
Subject: Re: Dynamic Partitioning using Segment Visibility Maps

pgsql-general by date

Next:From: Naz GassiepDate: 2008-01-07 14:49:53
Subject: Re: Hash Indexes
Previous:From: GeoffreyDate: 2008-01-07 14:07:36
Subject: Re: Memory on 32bit machine

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