pgsql: pg_regress: Promptly detect failed postmaster startup.

From: Noah Misch <noah(at)leadboat(dot)com>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: pg_regress: Promptly detect failed postmaster startup.
Date: 2018-12-31 22:18:36
Message-ID: E1ge5tM-0000n6-W0@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

pg_regress: Promptly detect failed postmaster startup.

Detect it the way pg_ctl's wait_for_postmaster() does. When pg_regress
spawned a postmaster that failed startup, we were detecting that only
with "pg_regress: postmaster did not respond within 60 seconds".
Back-patch to 9.4 (all supported versions).

Reviewed by Tom Lane.

Discussion: https://postgr.es/m/20181231172922.GA199150@gust.leadboat.com

Branch
------
REL_10_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/7c97b0f55e751297a5e30c0de28a779b945aa706

Modified Files
--------------
src/test/regress/pg_regress.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Noah Misch 2018-12-31 22:18:37 pgsql: pg_regress: Promptly detect failed postmaster startup.
Previous Message Tom Lane 2018-12-31 21:38:18 pgsql: Update leakproofness markings on some btree comparison functions