pgsql: Don't reset additional columns on subscriber to NULL on UPDATE

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Don't reset additional columns on subscriber to NULL on UPDATE
Date: 2017-11-03 16:35:03
Message-ID: E1eAevv-0002Hs-IS@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Don't reset additional columns on subscriber to NULL on UPDATE

When a publisher table has fewer columns than a subscriber, the update
of a row on the publisher should result in updating of only the columns
in common. The previous coding mistakenly reset the values of
additional columns on the subscriber to NULL because it failed to skip
updates of columns not found in the attribute map.

Author: Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/a9fce66729ad5217e8219e22e595974059c21291

Modified Files
--------------
src/backend/replication/logical/worker.c | 7 ++-
src/test/subscription/t/008_diff_schema.pl | 80 ++++++++++++++++++++++++++++++
2 files changed, 85 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-11-03 18:02:46 Re: pgsql: Fix BRIN summarization concurrent with extension
Previous Message Alvaro Herrera 2017-11-03 16:23:42 pgsql: Fix BRIN summarization concurrent with extension