From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: master in standby mode croaks |
Date: | 2010-04-01 23:06:13 |
Message-ID: | 1270163173.5640.3274.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2010-03-30 at 22:40 -0400, Robert Haas wrote:
> 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 don't think it is the same thing at all. This is a separate error and
should be rejected as such.
> I still think we need to fix this.
Agreed, as a separate issue.
--
Simon Riggs www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Pei He | 2010-04-02 02:02:50 | Problem of Magic Block in Postgres 8.2 |
Previous Message | Simon Riggs | 2010-04-01 22:55:46 | Re: [HACKERS] Streaming replication document improvements |