Robert Haas <robertmh...@gmail.com> writes:
> On Fri, Apr 23, 2010 at 4:10 PM, Heikki Linnakangas
> <heikki.linnakan...@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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
