Alvaro Herrera c2e0954be3 Relax overly strict assertion ... Ever since its birth, ReorderBufferBuildTupleCidHash() has contained an assertion that a catalog tuple cannot change Cmax after acquiring one. But that's wrong: if a subtransaction executes DDL that affects that catalog tuple, and later aborts and another DDL affects the same tuple, it will change Cmax. Relax the assertion to merely verify that the Cmax remains valid and monotonically increasing, instead. Add a test that tickles the relevant code. Diagnosed by, and initial patch submitted by: Arseny Sher Co-authored-by: Arseny Sher Discussion: https://postgr.es/m/874l9p8hyw.fsf@ars-thinkpad		2019-02-12 18:42:37 -03:00
..
binary.out
concurrent_ddl_dml.out
ddl.out	Relax overly strict assertion	2019-02-12 18:42:37 -03:00
decoding_in_xact.out
decoding_into_rel.out
delayed_startup.out
messages.out
mxact.out
oldest_xmin.out
ondisk_startup.out
permissions.out
prepared.out
replorigin.out
rewrite.out
slot.out
snapshot_transfer.out
spill.out
time.out
toast.out
truncate.out
xact.out