Re: GIN index creation extremely slow ? - Mailing list pgsql-hackers

From Stefan Kaltenbrunner
Subject Re: GIN index creation extremely slow ?
Date
Msg-id 44A543F6.7080303@kaltenbrunner.cc
Whole thread Raw
In response to Re: GIN index creation extremely slow ?  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-hackers
Teodor Sigaev wrote:
>> Tom did commit a patch a while ago which made a huge difference in
>> index creation time for tsearch by changing one routine. I don't know
>> if it got backpatched, so it might be worth checking people are working
>> on the same version.
> 
> I saw that patch, but I still think that 7 minutes is too small :)

hmm I did some further testing on that and it looks like you might
indeed be right in suspecting that there is something fishy with the
GIST results.
It might be possible that there was some issue with the generated
tsvectors (all of them empty due to hitting the "too long value" error
case for exceeding MAXSTRPOS) in the GIST case - sorry for the confusion:-(

Speaking of the "too long value" error message - some of the
errormessages in tsvector.c are a bit "terse" (ie it is not really
obvious what is causing the above error without looking at the source
for example).


Stefan


pgsql-hackers by date:

Previous
From: "Marko Kreen"
Date:
Subject: Re: Index corruption
Next
From: Jan Wieck
Date:
Subject: Re: Index corruption