Skip site navigation (1) Skip section navigation (2)

Re: tsvector_update_trigger performance?

From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Chris St Denis <lists(at)on-track(dot)ca>, pgsql-performance(at)postgresql(dot)org
Subject: Re: tsvector_update_trigger performance?
Date: 2009-06-24 20:03:21
Message-ID: (view raw or whole thread)
Lists: pgsql-performance

Le 24 juin 09 à 18:29, Alvaro Herrera a écrit :
> Oleg Bartunov wrote:
>> On Wed, 24 Jun 2009, Chris St Denis wrote:
>>> Is tsvector_update_trigger() smart enough to not bother updating a
>>> tsvector if the text in that column has not changed?
>> no, you should do check yourself. There are several examples in  
>> mailing lists.
> Or you could try using the supress_redundant_updates_trigger()  
> function
> that has been included in 8.4 (should be easy to backport)

But it won't handle the case where some other random column has  
changed, but the UPDATE is not affecting the text indexed...

In response to


pgsql-performance by date

Next:From: Chris St DenisDate: 2009-06-25 04:03:08
Subject: Re: tsvector_update_trigger performance?
Previous:From: Scott MarloweDate: 2009-06-24 17:42:08
Subject: Re: cluster index on a table

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group