Subscriber resets additional columns to NULL on UPDATE
Hi,
I found bug in logical replication where extra (nullable) columns on
subscriber will be reset to NULL value when update comes from provider.
The issue is apparently that we /points finger at himself/ forgot to
check specifically for columns that are not part of attribute map in
slot_modify_cstrings() so the extra columns will fall through to the
else block which sets the value to NULL.
Attached patch fixes it and adds couple of tests for this scenario.
This is rather serious issue so it would be good if we could get it
fixed in 10.1.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Attachments:
0001-Don-t-reset-additional-columns-on-subscriber-to-NULL.patchtext/x-patch; name=0001-Don-t-reset-additional-columns-on-subscriber-to-NULL.patchDownload+82-3
On 10/26/17 05:20, Petr Jelinek wrote:
I found bug in logical replication where extra (nullable) columns on
subscriber will be reset to NULL value when update comes from provider.The issue is apparently that we /points finger at himself/ forgot to
check specifically for columns that are not part of attribute map in
slot_modify_cstrings() so the extra columns will fall through to the
else block which sets the value to NULL.Attached patch fixes it and adds couple of tests for this scenario.
This is rather serious issue so it would be good if we could get it
fixed in 10.1.
done
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers