Re: pgsql: Only WAL-log the modified portion in an UPDATE, if possible. - Mailing list pgsql-committers

From Simon Riggs
Subject Re: pgsql: Only WAL-log the modified portion in an UPDATE, if possible.
Date
Msg-id CA+U5nMKxZCC9cSjrCJV2m51+_rX3MeDSA0g5krZF4tBgTKFJdg@mail.gmail.com
Whole thread Raw
In response to pgsql: Only WAL-log the modified portion in an UPDATE, if possible.  (Heikki Linnakangas <heikki.linnakangas@iki.fi>)
List pgsql-committers
On 12 March 2014 21:30, Heikki Linnakangas <heikki.linnakangas@iki.fi> wrote:
> Only WAL-log the modified portion in an UPDATE, if possible.
>
> When a row is updated, and the new tuple version is put on the same page as
> the old one, only WAL-log the part of the new tuple that's not identical to
> the old. This saves significantly on the amount of WAL that needs to be
> written, in the common case that most fields are not modified.
>
> Amit Kapila, with a lot of back and forth with me, Robert Haas, and others.

Nice tight, useful patch. Very neat, well done all.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-committers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: pgsql: Only WAL-log the modified portion in an UPDATE, if possible.
Next
From: Bruce Momjian
Date:
Subject: pgsql: C comments: remove odd blank lines after #ifdef WIN32 lines