PGSTAT start failure probably shouldn't disable Postgres

Started by Tom Laneabout 24 years ago2 messageshackers
Jump to latest
#1Tom Lane
tgl@sss.pgh.pa.us

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

#2Bruce Momjian
bruce@momjian.us
In reply to: Tom Lane (#1)
Re: PGSTAT start failure probably shouldn't disable Postgres

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 address

It 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