Re: [HACKERS] Subscriber resets additional columns to NULL on UPDATE - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Subscriber resets additional columns to NULL on UPDATE
Date
Msg-id c62be3dc-f7e1-97fc-88bd-d6307feb2d18@2ndquadrant.com
Whole thread Raw
In response to [HACKERS] Subscriber resets additional columns to NULL on UPDATE  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
List pgsql-hackers
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

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] MERGE SQL Statement for PG11
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] Proposal: Local indexes for partitioned table