| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: still gin index creation takes forever |
| Date: | 2008-11-13 13:36:33 |
| Message-ID: | 5440.1226583393@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I see. So this could explain Ivan's issue if his table contains
>> large numbers of repeated GIN keys. Ivan, is that what your data
>> looks like?
> Well if by GIN keys you mean lexemes it could be. But I wouldn't say
> this circumstance is uncommon among users of tsearch. I'd expect
> other people had used tsearch2 to search through titles, authors and
> publishers of books, so if that was the problem I'd expect the
> problem to come up earlier.
Yeah, I'm not convinced either. Still, Teodor's theory should be easily
testable: set synchronize_seqscans to FALSE and see if the problem goes
away.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adriana Alfonzo | 2008-11-13 13:39:50 | Re: Upgrading side by side in Gentoo |
| Previous Message | Holger Hoffstaette | 2008-11-13 13:30:52 | Re: Upgrading side by side in Gentoo |