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

From Robert Haas
Subject Re: recovery_connections cannot start (was Re: master in standby mode croaks)
Date
Msg-id j2l603c8f071004231443ub2bfc515wa1f38492aaeba9d6@mail.gmail.com
Whole thread Raw
In response to Re: recovery_connections cannot start (was Re: master in standby mode croaks)  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: recovery_connections cannot start (was Re: master in standby mode croaks)  (Simon Riggs <simon@2ndQuadrant.com>)
Re: recovery_connections cannot start (was Re: master in standby mode croaks)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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".

...Robert


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: recovery_connections cannot start (was Re: master in standby mode croaks)
Next
From: Simon Riggs
Date:
Subject: Re: recovery_connections cannot start (was Re: master in standby mode croaks)