| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Don't propagate a null subtransaction snapshot up to parent tran |
| Date: | 2016-08-07 17:16:15 |
| Message-ID: | E1bWRgN-00033x-T7@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Don't propagate a null subtransaction snapshot up to parent transaction.
This oversight could cause logical decoding to fail to decode an outer
transaction containing changes, if a subtransaction had an XID but no
actual changes. Per bug #14279 from Marko Tiikkaja. Patch by Marko
based on analysis by Andrew Gierth.
Discussion: <20160804191757(dot)1430(dot)39011(at)wrigleys(dot)postgresql(dot)org>
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/bcbecbce2fde3c6dfa9080db11663877808a007d
Modified Files
--------------
contrib/test_decoding/expected/xact.out | 24 +++++++++++++++++++++++-
contrib/test_decoding/sql/xact.sql | 13 ++++++++++++-
src/backend/replication/logical/reorderbuffer.c | 9 +++++----
3 files changed, 40 insertions(+), 6 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-08-07 18:36:07 | pgsql: Avoid crashing in GetOldestSnapshot() if there are no known snap |
| Previous Message | Tom Lane | 2016-08-07 02:08:38 | pgsql: First-draft release notes for 9.5.4. |