| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> |
| Cc: | pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Only WAL-log the modified portion in an UPDATE, if possible. |
| Date: | 2014-03-12 22:03:08 |
| Message-ID: | CA+U5nMKxZCC9cSjrCJV2m51+_rX3MeDSA0g5krZF4tBgTKFJdg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On 12 March 2014 21:30, Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-03-13 05:34:51 | pgsql: C comments: remove odd blank lines after #ifdef WIN32 lines |
| Previous Message | Heikki Linnakangas | 2014-03-12 21:30:28 | pgsql: Only WAL-log the modified portion in an UPDATE, if possible. |