pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Make sure to run pg_isready on correct port 7+ messages / 1 participants [nested] [flat]
* pgsql: Make sure to run pg_isready on correct port @ 2024-07-13 12:15 Andrew Dunstan <andrew@dunslane.net> 0 siblings, 0 replies; 7+ messages in thread From: Andrew Dunstan @ 2024-07-13 12:15 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 ------ master Details ------- https://git.postgresql.org/pg/commitdiff/055891f374a347aedd53c5b4fc79caf0a5522e18 Modified Files -------------- src/bin/scripts/t/080_pg_isready.pl | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Make sure to run pg_isready on correct port @ 2024-07-13 12:15 Andrew Dunstan <andrew@dunslane.net> 0 siblings, 0 replies; 7+ messages in thread From: Andrew Dunstan @ 2024-07-13 12:15 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Make sure to run pg_isready on correct port @ 2024-07-13 12:15 Andrew Dunstan <andrew@dunslane.net> 0 siblings, 0 replies; 7+ messages in thread From: Andrew Dunstan @ 2024-07-13 12:15 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/dd12eb33aff94dabee03d32a98d80dfa434805a6 Modified Files -------------- src/bin/scripts/t/080_pg_isready.pl | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Make sure to run pg_isready on correct port @ 2024-07-13 12:15 Andrew Dunstan <andrew@dunslane.net> 0 siblings, 0 replies; 7+ messages in thread From: Andrew Dunstan @ 2024-07-13 12:15 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/53a14ec29024e8060755e462c384bc6c323dee14 Modified Files -------------- src/bin/scripts/t/080_pg_isready.pl | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Make sure to run pg_isready on correct port @ 2024-07-13 12:15 Andrew Dunstan <andrew@dunslane.net> 0 siblings, 0 replies; 7+ messages in thread From: Andrew Dunstan @ 2024-07-13 12:15 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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_16_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/75f4ae2b8065ca7d29bec55f261828f794fbba1e Modified Files -------------- src/bin/scripts/t/080_pg_isready.pl | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Make sure to run pg_isready on correct port @ 2024-07-13 12:15 Andrew Dunstan <andrew@dunslane.net> 0 siblings, 0 replies; 7+ messages in thread From: Andrew Dunstan @ 2024-07-13 12:15 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/c5b15c417140b2b18b590d201b2fdb7b587214fd Modified Files -------------- src/bin/scripts/t/080_pg_isready.pl | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Make sure to run pg_isready on correct port @ 2024-07-13 12:15 Andrew Dunstan <andrew@dunslane.net> 0 siblings, 0 replies; 7+ messages in thread From: Andrew Dunstan @ 2024-07-13 12:15 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/6f55b4f112ab72ad392b0acfd5bf9b827e9bb458 Modified Files -------------- src/bin/scripts/t/080_pg_isready.pl | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2024-07-13 12:15 UTC | newest] Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2024-07-13 12:15 pgsql: Make sure to run pg_isready on correct port Andrew Dunstan <andrew@dunslane.net> 2024-07-13 12:15 pgsql: Make sure to run pg_isready on correct port Andrew Dunstan <andrew@dunslane.net> 2024-07-13 12:15 pgsql: Make sure to run pg_isready on correct port Andrew Dunstan <andrew@dunslane.net> 2024-07-13 12:15 pgsql: Make sure to run pg_isready on correct port Andrew Dunstan <andrew@dunslane.net> 2024-07-13 12:15 pgsql: Make sure to run pg_isready on correct port Andrew Dunstan <andrew@dunslane.net> 2024-07-13 12:15 pgsql: Make sure to run pg_isready on correct port Andrew Dunstan <andrew@dunslane.net> 2024-07-13 12:15 pgsql: Make sure to run pg_isready on correct port Andrew Dunstan <andrew@dunslane.net>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox