diff options
| author | Michael Paquier <michael@paquier.xyz> | 2025-07-29 17:03:07 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2025-07-29 17:03:07 +0900 |
| commit | cb833c1b6d19507b13a1a852feea4dbe5d6f0c20 (patch) | |
| tree | 1fde156036df3b50e5b499ceb33d388be2f51561 /contrib/postgres_fdw/postgres_fdw.c | |
| parent | c2c2c7e225669e81f83a5db3f0f57131cdaa4a2d (diff) | |
| download | postgresql-cb833c1b6d19507b13a1a852feea4dbe5d6f0c20.tar.gz postgresql-cb833c1b6d19507b13a1a852feea4dbe5d6f0c20.zip | |
Handle timeout in PostgreSQL::Test::Cluster::is_alive()
This commit adds an extra --timeout=PG_TEST_TIMEOUT_DEFAULT to the call
of pg_isready done in is_alive(), so as it is possible to have more
leverage with the call on machines constrained on resources.
By default the timeout is 180s, and it can be changed depending on the
environment where the tests are run.
Per buildfarm member mamba, where the default timeout of 3s used by
pg_isready has proved that it may not be enough as the postmaster may
not have the time it needs to reply to a ping request.
Reported-by: Alexander Lakhin <exclusion@gmail.com>
Reviewed-by: Nazir Bilal Yavuz <byavuz81@gmail.com>
Discussion: https://postgr.es/m/29b637df-f818-4b52-986a-f11ba28300e9@gmail.com
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions