| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: very long update gin index troubles back? |
| Date: | 2009-01-24 12:54:37 |
| Message-ID: | 497B0F8D.6060905@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
GIN index is slow for update by its construction. When you update the rows with
or without columns indexed by GIN, postgres (in most cases) will insert new
records, so index insertion will occur. So, for large updates it's much cheaper
to drop and create index.
That was a one of reasons to develop fast_insert_gin patch which now in review
process.
Ivan Sergio Borgonovo wrote:
> I've a table that contain a tsvector that is indexed (gin) and
> triggers to update the tsvector that should then update the index.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Sollars | 2009-01-24 16:23:09 | dblink syntax question for remotely invoking void-returning procedures |
| Previous Message | Oleg Bartunov | 2009-01-24 12:29:26 | Re: very long update gin index troubles back? |