pgsql: tests: Don't fail due to high default timeout in postmaster/003_

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: tests: Don't fail due to high default timeout in postmaster/003_
Date: 2025-03-07 18:22:56
Message-ID: E1tqcLY-001Iqx-1v@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

tests: Don't fail due to high default timeout in postmaster/003_start_stop

Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.

As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.

Per buildfarm animal skink.

Reviewed-by: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/b48832cddbf57a3428f1a553e395f1870e1b0cb5

Modified Files
--------------
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2025-03-07 18:24:29 pgsql: Include column name in build_attrmap_by_position's error reports
Previous Message Álvaro Herrera 2025-03-07 18:20:34 Re: pgsql: reindexdb: Add the index-level REINDEX with multiple jobs