Subscriber resets additional columns to NULL on UPDATE
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t37622psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 27, 2026 at 09:59 PM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t37622_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t37622_1 && git checkout t37622_1Patchset v1 (message #1) is on t37622_1
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
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