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.jeli...@2ndquadrant.com> Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/a14b52c61454e3d23f7d0ab0affa56f8abfdf505 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(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
