| From: | Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> |
|---|---|
| To: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | New isolation test insert-conflict-do-update-4 outputs rows in alternative ordering |
| Date: | 2026-02-24 16:13:02 |
| Message-ID: | CALT9ZEHcE6tpvumScYPO6pGk_ASjTjWojLkodHnk33dvRPHXVw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Fix-sorting-of-output-rows-in-a-new-isolation-tes.patch | application/octet-stream | 2.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2026-02-24 16:15:01 | Re: Add errdetail() with PID and UID about source of termination signal |
| Previous Message | Álvaro Herrera | 2026-02-24 16:12:41 | Re: Fix bug of clearing of waitStart in ProcWakeup() |