| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: recovery_connections cannot start (was Re: master in standby mode croaks) |
| Date: | 2010-04-23 22:03:56 |
| Message-ID: | 1272060236.4161.844.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2010-04-23 at 17:43 -0400, Robert Haas wrote:
> On Fri, Apr 23, 2010 at 4:10 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)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".
We don't need *both* wal_mode and archive_mode, since archive_mode
exists only to ensure that full WAL is written even when archive_command
= '' momentarily.
Should do this
> > wal_mode=crash/archive/standby
> > archive_command='command'
> > max_wal_senders=<integer> # if > 0, wal_mode must be >= 'archive'
and make wal_mode SIGHUP
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pasher | 2010-04-23 22:06:04 | Re: Postgres stats collector showing high disk I/O |
| Previous Message | Justin Pasher | 2010-04-23 21:49:38 | Re: Postgres stats collector showing high disk I/O |