Re: Dirty buffers with suppress_redundant_updates_trigger - Mailing list pgsql-general

From Mike Noordermeer
Subject Re: Dirty buffers with suppress_redundant_updates_trigger
Date
Msg-id CAF0ozqvN9bsPNZ-K9nE4eKETi7O1dhm_=wB5Cj5oEmC3DPVQDA@mail.gmail.com
Whole thread Raw
In response to Re: Dirty buffers with suppress_redundant_updates_trigger  (Mike Noordermeer <mike@normi.net>)
Responses Re: Dirty buffers with suppress_redundant_updates_trigger  (Michael Lewis <mlewis@entrata.com>)
List pgsql-general
For future reference, in the end I have just added a WHERE clause
comparing all fields with IS DISTINCT FROM. This seems to work well,
prevents any locks/WAL-generation and is about as fast as the previous
solution with suppress_redundant_updates_trigger().

Kind regards,

Mike



pgsql-general by date:

Previous
From: luis.roberto@siscobra.com.br
Date:
Subject: Effective IO Concurrency
Next
From: Michael Lewis
Date:
Subject: Re: Dirty buffers with suppress_redundant_updates_trigger