Re: Inherit regression outputs rows in alternative ordering when run on other table AM than heap
Pavel Borisov <pashkin.elfe@gmail.com>
From: Pavel Borisov <pashkin.elfe@gmail.com>
To: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-03-27T13:45:09Z
Lists: pgsql-hackers
Attachments
- v2-0001-Stabilize-output-of-inherit-regression-test.patch (application/octet-stream) patch v2-0001
- v2-0002-Stabilize-output-of-join-regression-test.patch (application/octet-stream) patch v2-0002
- v2-0003-Stabilize-output-of-updatable_views-regression-te.patch (application/octet-stream) patch v2-0003
Hi, hackers! On Fri, 27 Mar 2026 at 16:54, Pavel Borisov <pashkin.elfe@gmail.com> wrote: > > Hi, hackers! > > Existing inherit regression test results are tied to the particular > row order after UPDATE clause. The context is approximately the same > as in [1]. > This could be easily fixed by adding ORDER BY clause to the test. See > the patch proposed. I added order by not only to places prone to the > difference quoted but also to other places as it's cheap and doesn't > harm. If the committer don't agree with extra order by's I can leave > only those necessary for fixing quoted test output. > > [1] https://github.com/postgres/postgres/commit/4c1a27e53a508f74883cda52a6c8612121d7fd6b To existing unchanged patch 0001, I've added a couple of others: 0002: Fixes join order differences. The patch fixes only particular fail that I'm seeing. 0003: Fixed updatable view order differences. It's carpet replacement of the test with adding ORDER BY's. Kind regards, Pavel Borisov Supabase
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Stabilize output of new isolation test insert-conflict-do-update-4.
- 4c1a27e53a50 19 (unreleased) cited