postgresql/src/test/subscription
Tom Lane a2aa224e05 Fix bogus tuple-slot management in logical replication UPDATE handling.
slot_modify_cstrings seriously abused the TupleTableSlot API by relying
on a slot's underlying data to stay valid across ExecClearTuple.  Since
this abuse was also quite undocumented, it's little surprise that the
case got broken during the v12 slot rewrites.  As reported in bug #16129
from Ondřej Jirman, this could lead to crashes or data corruption when
a logical replication subscriber processes a row update.  Problems would
only arise if the subscriber's table contained columns of pass-by-ref
types that were not being copied from the publisher.

Fix by explicitly copying the datum/isnull arrays from the source slot
that the old row was in already.  This ends up being about the same
thing that happened pre-v12, but hopefully in a less opaque and
fragile way.

We might've caught the problem sooner if there were any test cases
dealing with updates involving non-replicated or dropped columns.
Now there are.

Back-patch to v10 where this code came in.  Even though the failure
does not manifest before v12, IMO this code is too fragile to leave
as-is.  In any case we certainly want the additional test coverage.

Patch by me; thanks to Tomas Vondra for initial investigation.

Discussion: https://postgr.es/m/16129-a0c0f48e71741e5f@postgresql.org
2019-11-22 11:31:19 -05:00
..
t Fix bogus tuple-slot management in logical replication UPDATE handling. 2019-11-22 11:31:19 -05:00
.gitignore Logical replication 2017-01-20 09:04:49 -05:00
Makefile Collations with nondeterministic comparison 2019-03-22 12:12:43 +01:00
README Clarify the README files for the various separate TAP-based test suites. 2018-06-19 19:30:50 -04:00

src/test/subscription/README

Regression tests for subscription/logical replication
=====================================================

This directory contains a test suite for subscription/logical replication.

Running the tests
=================

NOTE: You must have given the --enable-tap-tests argument to configure.

Run
    make check
or
    make installcheck
You can use "make installcheck" if you previously did "make install"
(including installing the hstore extension).  In that case, the code
in the installation tree is tested.  With "make check", a temporary
installation tree is built from the current sources and then tested.

Either way, this test initializes, starts, and stops several test Postgres
clusters.