Re: Inherit regression outputs rows in alternative ordering when run on other table AM than heap - Mailing list pgsql-hackers

From John Naylor
Subject Re: Inherit regression outputs rows in alternative ordering when run on other table AM than heap
Date
Msg-id CANWCAZYBKjZndN69y0-1OWNfkD9wjJWpDUZTYe=G8phOnh1PMw@mail.gmail.com
Whole thread
In response to Inherit regression outputs rows in alternative ordering when run on other table AM than heap  (Pavel Borisov <pashkin.elfe@gmail.com>)
Responses Re: Inherit regression outputs rows in alternative ordering when run on other table AM than heap
List pgsql-hackers
On Fri, Mar 27, 2026 at 7:54 PM Pavel Borisov <pashkin.elfe@gmail.com> wrote:
> Existing inherit regression test results are tied to the particular
> row order after UPDATE clause. The context is approximately the same
> as in [1].
>
> When run on different table AM it shows the following difference in output:

I think it'd be beneficial to make regression tests more reproducible
across different table AMs. It's worth asking how much the ongoing
maintenance cost would be, since I imagine the one you're testing is
not the only one that shows differences.

--
John Naylor
Amazon Web Services



pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: off-by-one in pg_repack index loop
Next
From: Hannu Krosing
Date:
Subject: Re: Support logical replication of DDLs, take2