Re: How to avoid UPDATE performance degradation in a transaction - Mailing list pgsql-performance

From Michael Lewis
Subject Re: How to avoid UPDATE performance degradation in a transaction
Date
Msg-id CAHOFxGpdHR5XaNmuRczmkGUnWop5uVdURuvVs0HBoi3Nrusi6g@mail.gmail.com
Whole thread Raw
In response to Re: How to avoid UPDATE performance degradation in a transaction  (Karl Düüna <karl.dyyna@gmail.com>)
List pgsql-performance
If your trigger is supposed to change certain fields, you could return OLD instead of NEW if those fields have not been changed by the trigger. You could also check an updated_on timestamp field to verify if the row has already been modified and potentially skip the trigger altogether. Just a couple thoughts to avoid the bloat.

pgsql-performance by date:

Previous
From: Karl Düüna
Date:
Subject: Re: How to avoid UPDATE performance degradation in a transaction
Next
From: MingJu Wu
Date:
Subject: Partial index creation always scans the entire table