| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Make sure to run pg_isready on correct port |
| Date: | 2024-07-13 12:15:11 |
| Message-ID: | E1sSbeh-001V3b-4W@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Make sure to run pg_isready on correct port
The current code can have pg_isready unexpectedly succeed if there is a
server running on the default port. To avoid this we delay running the
test until after a node has been created but before it starts, and then
use that node's port, so we are fairly sure there is nothing running on
the port.
Backpatch to all live branches.
Branch
------
REL_13_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/2423c84d098ab47ae540bc88a29bcb6fb3812e60
Modified Files
--------------
src/bin/scripts/t/080_pg_isready.pl | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2024-07-13 15:11:06 | pgsql: Don't lose partitioned table reltuples=0 after relhassubclass=f. |
| Previous Message | Andrew Dunstan | 2024-07-13 12:15:10 | pgsql: Make sure to run pg_isready on correct port |