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

From: Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>
To: 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-24 18:52:00
Message-ID: CALT9ZEFGnw-_umXR5KBXBPnt1oMq_XXqPQvzKWMTEFH6Kr8LwQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

This fix should also be backported to all releases that have commit
4b760a181ab2 backported.

Pavel Borisov

On Tue, 24 Feb 2026 at 20:13, Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> wrote:
>
> Hi, hackers!
>
> 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.
>
> Other insert-conflict-do-* isolation tests output just one row except
> the mentioned insert-conflict-do-update-3 and
> insert-conflict-do-update-4.
>
> The patch is attached
>
> Kind regards,
> Pavel Borisov
> Supabase

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2026-02-24 18:58:30 Re: pgsql: libpq: Grease the protocol by default
Previous Message Tom Lane 2026-02-24 18:50:33 Re: pgsql: libpq: Grease the protocol by default