From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Fix logical replication launcher wake up and reset |
Date: | 2017-05-01 14:22:07 |
Message-ID: | E1d5CDH-0006Mk-6v@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Fix logical replication launcher wake up and reset
After the logical replication launcher was told to wake up at
commit (for example, by a CREATE SUBSCRIPTION command), the flag to wake
up was not reset, so it would be woken up at every following commit as
well. So fix that by resetting the flag.
Also, we don't need to wake up anything if the transaction was rolled
back. Just reset the flag in that case.
Author: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Reported-by: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/9414e41ea703ea5fcc288bcf7dc000e53306896b
Modified Files
--------------
src/backend/access/transam/xact.c | 3 ++-
src/backend/replication/logical/launcher.c | 6 ++++--
src/include/replication/logicallauncher.h | 2 +-
3 files changed, 7 insertions(+), 4 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2017-05-01 14:57:28 | pgsql: Allow vcregress.pl to run an arbitrary TAP test set |
Previous Message | Robert Haas | 2017-05-01 12:29:15 | pgsql: Fire per-statement triggers on partitioned tables. |