From: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
---|---|
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-28 20:38:47 |
Message-ID: | Pine.LNX.4.64.0901282337330.9554@sn.sai.msu.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 28 Jan 2009, Ivan Sergio Borgonovo wrote:
> On Tue, 27 Jan 2009 20:45:53 +0300
> Teodor Sigaev <teodor(at)sigaev(dot)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(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83
From | Date | Subject | |
---|---|---|---|
Next Message | aws | 2009-01-28 22:29:57 | libpq binary format for contrib/cube type? |
Previous Message | Ivan Sergio Borgonovo | 2009-01-28 20:14:24 | Re: very long update gin index troubles back? |