pgsql: Set ActiveSnapshot when logically replaying inserts - Mailing list pgsql-committers

From Alvaro Herrera
Subject pgsql: Set ActiveSnapshot when logically replaying inserts
Date
Msg-id E1fkEpi-0002q7-4U@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Set ActiveSnapshot when logically replaying inserts

Input functions for the inserted tuples may require a snapshot, when
they are replayed by native logical replication.  An example is a domain
with a constraint using a SQL-language function, which prior to this
commit failed to apply on the subscriber side.

Reported-by: Mai Peng <maily.peng@webedia-group.com>
Co-authored-by: Minh-Quan TRAN <qtran@itscaro.me>
Co-authored-by: Álvaro Herrera <alvherre@alvh.no-ip.org>
Discussion: https://postgr.es/m/4EB4BD78-BFC3-4D04-B8DA-D53DF7160354@webedia-group.com
Discussion: https://postgr.es/m/153211336163.1404.11721804383024050689@wrigleys.postgresql.org

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/5dbd0beb8a95fa1de3a931d20102cc9f273fceef

Modified Files
--------------
src/backend/replication/logical/worker.c |  4 +++-
src/test/subscription/t/002_types.pl     | 24 ++++++++++++++++++++++--
2 files changed, 25 insertions(+), 3 deletions(-)


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: doc: Improve CREATE COLLATION locking documentation
Next
From: Tom Lane
Date:
Subject: pgsql: Ensure we build generated headers at the start of some morecase