Re: Inherit regression outputs rows in alternative ordering when run on other table AM than heap

From: John Naylor <johncnaylorls(at)gmail(dot)com>
To: Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Inherit regression outputs rows in alternative ordering when run on other table AM than heap
Date: 2026-04-29 07:49:16
Message-ID: CANWCAZYBKjZndN69y0-1OWNfkD9wjJWpDUZTYe=G8phOnh1PMw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 27, 2026 at 7:54 PM Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2026-04-29 08:07:04 Re: Support logical replication of DDLs, take2
Previous Message John Naylor 2026-04-29 07:16:08 Re: off-by-one in pg_repack index loop