Re: Re: [WIP] Performance Improvement by reducing WAL for Update Operation
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Noah Misch <noah@leadboat.com>
Cc: Amit kapila <amit.kapila@huawei.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, "'Heikki Linnakangas'" <heikki.linnakangas@enterprisedb.com>
Date: 2012-09-27T04:48:39Z
Lists: pgsql-hackers
Noah Misch <noah@leadboat.com> writes: > You cannot assume executor-unmodified columns are also unmodified from > heap_update()'s perspective. Expansion in one column may instigate TOAST > compression of a logically-unmodified column, and that counts as a change for > xlog delta purposes. Um ... what about BEFORE triggers? Frankly, I think that expecting the executor to tell you which columns have been modified is a non-starter. We have a solution for HOT and it's silly to do the same thing differently just a few lines away. regards, tom lane