Re: Improve error reporting in 027_stream_regress test

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Bilal Yavuz <byavuz81@gmail.com>
Cc: Brandon Tat <brandontat6@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Alexander Lakhin <exclusion@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Andres Freund <andres@anarazel.de>
Date: 2025-12-06T05:45:13Z
Lists: pgsql-hackers
On Fri, Dec 05, 2025 at 10:50:25AM +0300, Bilal Yavuz wrote:
> I liked your version more. My only complaint was removing the
> line_count argument but we can easily add it back when we need it.

Yes, I am not sure about that at this stage.  It would be good to see
more use cases for this new API before deciding anything, to let the
callers of this new routine enforce their fate.

> You are right, thank you for handling that.

Okay, applied then.  That should close this thread.
--
Michael

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Improve error reporting of recovery test 027_stream_regress

  2. Add PostgreSQL::Test::Cluster::read_head_tail() helper to PostgreSQL/Utils.pm

  3. Handle timeout in PostgreSQL::Test::Cluster::is_alive()

  4. Check status of nodes after regression test run in 027_stream_regress

  5. Add PostgreSQL::Test::Cluster::is_alive()