Re: recovery_connections cannot start (was Re: master in standby mode croaks) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: recovery_connections cannot start (was Re: master in standby mode croaks)
Date
Msg-id 18410.1272061800@sss.pgh.pa.us
Whole thread Raw
In response to Re: recovery_connections cannot start (was Re: master in standby mode croaks)  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: recovery_connections cannot start (was Re: master in standby mode croaks)  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Apr 23, 2010 at 4:10 PM, Heikki Linnakangas
> <heikki.linnakangas@enterprisedb.com> wrote:
>> So my proposal would be:
>> 
>> wal_mode=crash/archive/standby
>> archive_mode=on/off             # if on, wal_mode must be >= 'archive'
>> archive_command='command'
>> max_wal_senders=<integer>       # if > 0, wal_mode must be >= 'archive'

> As a general design comment, I think we should avoid still having an
> archive_mode GUC but having it do something different.  If we're going
> to change the semantics, we should also change the name, maybe to
> "archiving".

Agreed on the general point, but AFAICS that proposal keeps the meaning
of archive_mode the same as it was.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct
Next
From: Tom Lane
Date:
Subject: Re: recovery_connections cannot start (was Re: master in standby mode croaks)