pgsql: Set ActiveSnapshot when logically replaying inserts

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Set ActiveSnapshot when logically replaying inserts
Date: 2018-07-30 20:31:58
Message-ID: E1fkEpi-0002q7-4U@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)peng(at)webedia-group(dot)com>
Co-authored-by: Minh-Quan TRAN <qtran(at)itscaro(dot)me>
Co-authored-by: Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-07-30 22:04:49 pgsql: Ensure we build generated headers at the start of some more case
Previous Message Peter Eisentraut 2018-07-30 20:12:41 pgsql: doc: Improve CREATE COLLATION locking documentation