Re: tsvector_update_trigger performance?

От: Craig Ringer
Тема: Re: tsvector_update_trigger performance?
Дата: ,
Msg-id: 1245908719.19608.4.camel@tillium.localnet
(см: обсуждение, исходный текст)
Ответ на: Re: tsvector_update_trigger performance?  (Chris St Denis)
Ответы: Re: tsvector_update_trigger performance?  (Dimitri Fontaine)
Список: pgsql-performance

Скрыть дерево обсуждения

tsvector_update_trigger performance?  (Chris St Denis, )
 Re: tsvector_update_trigger performance?  (Oleg Bartunov, )
  Re: tsvector_update_trigger performance?  (Alvaro Herrera, )
   Re: tsvector_update_trigger performance?  (Dimitri Fontaine, )
    Re: tsvector_update_trigger performance?  (Chris St Denis, )
     Re: tsvector_update_trigger performance?  (Craig Ringer, )
      Re: tsvector_update_trigger performance?  (Dimitri Fontaine, )

On Wed, 2009-06-24 at 21:03 -0700, Chris St Denis wrote:
> This sounds like something that should just be on by default, not a
> trigger. Is there some reason it would waste the io of writing a new row
> to disk if nothing has changed? or is it just considered too much
> unnecessary overhead to compare them?

I think the theory is that carefully written applications generally do
not generate redundant updates in the first place. An application that
avoids redundant updates should not have to pay the cost of redundant
update detection and elimination.

--
Craig Ringer



В списке pgsql-performance по дате сообщения:

От: Dimitri Fontaine
Дата:
Сообщение: Re: tsvector_update_trigger performance?
От: Mike Ivanov
Дата:
Сообщение: Re: Implications of having large number of users