Re: Assertion failure in walreceiver - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Assertion failure in walreceiver
Date
Msg-id 407d949e1002251911y4998255av84931a1b033f5e49@mail.gmail.com
Whole thread Raw
In response to Re: Assertion failure in walreceiver  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Assertion failure in walreceiver  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Thu, Feb 25, 2010 at 7:31 AM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> While we're at it, the error message doesn't seem right:
>
> FATAL:  recovery connections cannot start because the
> recovery_connections parameter is disabled on the WAL source server
>
> recovery_connections is on by default, the real problem is that
> archive_command and max_wal_senders are disabled.

So do I understand this right, if you have archive_mode disabled and
try to start a slave you get this error. Then when you shut down your
master and set archive_mode on and bring it up and try again you'll
*still* get this message because the last checkpoint will be the final
shutdown checkpoint where  archive_mode was still disabled?


--
greg


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: A thought: should we run pgindent now?
Next
From: Robert Haas
Date:
Subject: Re: Avoiding bad prepared-statement plans.