Subject: pgsql: Stabilize output of new isolation test insert-conflict-do-update

From: Tom Lane <[email-masked]>
Date: Wed, 25 Feb 2026 15:51:56 +0000

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 <[email-masked]>
Reviewed-by: Tom Lane <[email-masked]>
Discussion: https://postgr.es/m/[email-masked]
Backpatch-through: 14

Branch
------
REL_18_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/aeaf2fc0ddbfb1e4a706555e33d9b4165d110a1c

Modified Files
--------------
src/test/isolation/expected/insert-conflict-do-update-4.out | 8 ++++----
src/test/isolation/specs/insert-conflict-do-update-4.spec   | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)