mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-08-13 16:13:26 +02:00
0bda14d54c
Somehow I managed to flip the order of restoring old & new tuples when de-spooling a change in a large transaction from disk. This happens to only take effect when a change is spooled to disk which has old/new versions of the tuple. That only is the case for UPDATEs where he primary key changed or where replica identity is changed to FULL. The tests didn't catch this because either spooled updates, or updates that changed primary keys, were tested; not both at the same time. Found while adding tests for the following commit. Backpatch: 9.4, where logical decoding was added |
||
|---|---|---|
| .. | ||
| binary.sql | ||
| ddl.sql | ||
| decoding_in_xact.sql | ||
| decoding_into_rel.sql | ||
| permissions.sql | ||
| prepared.sql | ||
| replorigin.sql | ||
| rewrite.sql | ||
| time.sql | ||
| toast.sql | ||
| xact.sql | ||