Horton

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

Pavel Borisov <pashkin.elfe@gmail.com>

View thread View on postgr.es
From: Pavel Borisov <pashkin.elfe@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-02-25T17:24:54Z
Lists: pgsql-hackers 
On Wed, 25 Feb 2026 at 19:52, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Pavel Borisov <pashkin.elfe@gmail.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
Thank you!
Regards,
Pavel Borisov

Commits

  1. Stabilize output of new isolation test insert-conflict-do-update-4.

  2. Remove faulty Assert in partitioned INSERT...ON CONFLICT DO UPDATE.