Re: very long update gin index troubles back? - Mailing list pgsql-general

From Oleg Bartunov
Subject Re: very long update gin index troubles back?
Date
Msg-id Pine.LNX.4.64.0901282337330.9554@sn.sai.msu.ru
Whole thread Raw
In response to Re: very long update gin index troubles back?  (Ivan Sergio Borgonovo <mail@webthatworks.it>)
Responses Re: very long update gin index troubles back?
List pgsql-general
On Wed, 28 Jan 2009, Ivan Sergio Borgonovo wrote:

> On Tue, 27 Jan 2009 20:45:53 +0300
> Teodor Sigaev <teodor@sigaev.ru> wrote:
>
>>> No matter if I drop the trigger that update agg content and the
>>> fact that I'm just updating d, postgresql will update the index?
>> Yes, due to MVCC. Update of row could produce new version (tuple)
>> and new version should be index as old one.
>
> Does that mean that it could be a good choice to place the tsvector
> in another table?

this is a trade-off - additional join

     Regards,
         Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83

pgsql-general by date:

Previous
From: Ivan Sergio Borgonovo
Date:
Subject: Re: very long update gin index troubles back?
Next
From: aws
Date:
Subject: libpq binary format for contrib/cube type?