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: | 877iil7kxw.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-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
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training!
From | Date | Subject | |
---|---|---|---|
Next Message | Naz Gassiep | 2008-01-07 14:49:53 | Re: Hash Indexes |
Previous Message | Geoffrey | 2008-01-07 14:07:36 | Re: Memory on 32bit machine |
From | Date | Subject | |
---|---|---|---|
Next Message | Usama Dar | 2008-01-07 14:49:47 | Re: Tuning Postgresql on Windows XP Pro 32 bit |
Previous Message | Csaba Nagy | 2008-01-07 13:32:03 | Re: Dynamic Partitioning using Segment Visibility Maps |