]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Stabilize output of new isolation test insert-conflict-do-update-4.
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 25 Feb 2026 15:51:42 +0000 (10:51 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 25 Feb 2026 15:51:42 +0000 (10:51 -0500)
commit0a2600e4cd525382212581267877ca6e5bbdf335
tree33f947ffd9e44baaf5a59efae66426d9dfb9e6b3
parentad7fc3f1f83f776812af27dbb747642dc88bba78
Stabilize output of new isolation test insert-conflict-do-update-4.

The test added by commit 4b760a181 assumed that a table's physical
row order would be predictable after an UPDATE.  But a non-heap table
AM might produce some other order.  Even with heap AM, the assumption
seems risky; compare a3fd53bab for instance.  Adding an ORDER BY is
cheap insurance and doesn't break any goal of the test.

Author: Pavel Borisov <pashkin.elfe@gmail.com>
Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: https://postgr.es/m/CALT9ZEHcE6tpvumScYPO6pGk_ASjTjWojLkodHnk33dvRPHXVw@mail.gmail.com
Backpatch-through: 14
src/test/isolation/expected/insert-conflict-do-update-4.out
src/test/isolation/specs/insert-conflict-do-update-4.spec