PGSTAT start failure probably shouldn't disable Postgres
We've seen several reports now of 7.2 postmasters failing to start
because of weird networking setups --- if it's impossible to create
a loopback UDP port on 127.0.0.1, 7.2 will exit with
PGSTAT: bind(2): Cannot assign requested address
It occurs to me that a more friendly behavior would be to disable
statistics gathering and proceed with startup anyway. Any objections?
regards, tom lane
Tom Lane wrote:
We've seen several reports now of 7.2 postmasters failing to start
because of weird networking setups --- if it's impossible to create
a loopback UDP port on 127.0.0.1, 7.2 will exit with
PGSTAT: bind(2): Cannot assign requested addressIt occurs to me that a more friendly behavior would be to disable
statistics gathering and proceed with startup anyway. Any objections?
Agreed. Throw an elog(LOG) and continue.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026