master in standby mode croaks - Mailing list pgsql-hackers

From Robert Haas
Subject master in standby mode croaks
Date
Msg-id k2l603c8f071003301940q4b7f7b6qac7bbe73f09edf3@mail.gmail.com
Whole thread Raw
Responses Re: master in standby mode croaks
List pgsql-hackers
I discovered tonight that if you shut down a server, create
recovery.conf with standby_mode = 'on', and start it back up again,
you get this:

LOG:  database system was shut down at 2010-03-30 22:34:09 EDT
LOG:  entering standby mode
FATAL:  recovery connections cannot start because the
recovery_connections parameter is disabled on the WAL source server
LOG:  startup process (PID 22980) exited with exit code 1
LOG:  aborting startup due to startup process failure

Now, you might certainly argue that this is a stupid thing to do (my
motivation was to test some stuff) but certainly it's fair to say that
error message is darn misleading, since in fact recovery_connections
was NOT disabled.  I believe this is the same "start up from a shut
down checkpoint" problem that's been discussed previously so I won't
belabor the point other than to say that I still think we need to fix
this.

...Robert


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Alpha release this week?
Next
From: Robert Haas
Date:
Subject: sorry, too many standbys already vs. MaxWalSenders vs. max_wal_senders