Horton
Menu

Re: Improve error reporting in 027_stream_regress test

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nazir Bilal Yavuz <byavuz81@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, Alexander Lakhin <exclusion@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Andres Freund <andres@anarazel.de>
Date: 2025-11-15T21:58:17Z
Lists: pgsql-hackers 
I wrote:
> Michael Paquier <michael@paquier.xyz> writes:
>> We are getting PQPING_NO_RESPONSE meaning a lack of report activity
>> from the postmaster.  An increase in timeout may help, but the host
>> seems like it's facing a high workload so it's not really possible to
>> come with a perfect number, just an estimation.  How about adding a
>> --timeout to pg_isready based on PGCONNECT_TIMEOUT, like in the
>> attached?

> +1 for lengthening the timeout, as I see you already did.

I just marked the CF entry for this thread committed [1], because I
saw that the cfbot was reporting its patch-of-record as committed.
However, looking back now at the thread, it looks like there was
some unfinished work from earlier patches.  If you are still
interested in pursuing that, please post a current patch to
de-confuse the bot and set the CF entry back to needs-review.

			regards, tom lane

[1] https://commitfest.postgresql.org/patch/5900/

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()