Re: recovery_connections cannot start (was Re: master in standby mode croaks)
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Simon Riggs <simon@2ndquadrant.com>, Kevin Grittner <Kevin.Grittner@wicourts.gov>, Fujii Masao <masao.fujii@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2010-04-23T22:30:00Z
Lists: 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