aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeWorktablescan.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2017-11-03 11:59:20 -0400
committerPeter Eisentraut <peter_e@gmx.net>2017-11-03 12:28:08 -0400
commita14b52c61454e3d23f7d0ab0affa56f8abfdf505 (patch)
treeb2a5c0e69a66516dcc8835595f679f3c9c8b44fb /src/backend/executor/nodeWorktablescan.c
parent37a856567c04cf48d38292afc487be5f2665c2a5 (diff)
downloadpostgresql-a14b52c61454e3d23f7d0ab0affa56f8abfdf505.tar.gz
postgresql-a14b52c61454e3d23f7d0ab0affa56f8abfdf505.zip
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.jelinek@2ndquadrant.com>
Diffstat (limited to 'src/backend/executor/nodeWorktablescan.c')
0 files changed, 0 insertions, 0 deletions