Re: New isolation test insert-conflict-do-update-4 outputs rows in alternative ordering

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: New isolation test insert-conflict-do-update-4 outputs rows in alternative ordering
Date: 2026-02-25 15:52:22
Message-ID: 184213.1772034742@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> writes:
> New isolation test insert-conflict-do-update-4 was added by commit 4b760a181ab2
> Unlike the previous test (insert-conflict-do-update-3) it doesn't
> contain an ordering clause, and when run on a table with a custom
> access method, it outputs results in a reverse order.
> It's a very minor issue, and the proposed fix is just adding the
> missing ORDER BY clause.

Right, done.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-02-25 15:55:30 Re: Warning-suppression fixes we ought to back-patch
Previous Message Peter Eisentraut 2026-02-25 15:43:07 Re: Warning-suppression fixes we ought to back-patch