Re: tsvector_update_trigger performance?
От | Dimitri Fontaine |
---|---|
Тема | Re: tsvector_update_trigger performance? |
Дата | |
Msg-id | 53BB722A-B50E-4831-9E6F-3CE15BEA9C30@hi-media.com обсуждение исходный текст |
Ответ на | Re: tsvector_update_trigger performance? (Alvaro Herrera <alvherre@commandprompt.com>) |
Ответы |
Re: tsvector_update_trigger performance?
|
Список | pgsql-performance |
Hi, 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) http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/backports/min_update/ http://blog.tapoueh.org/projects.html#sec9 But it won't handle the case where some other random column has changed, but the UPDATE is not affecting the text indexed... -- dim
В списке pgsql-performance по дате отправления: