| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, 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 21:43:00 |
| Message-ID: | j2l603c8f071004231443ub2bfc515wa1f38492aaeba9d6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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".
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pasher | 2010-04-23 21:49:38 | Re: Postgres stats collector showing high disk I/O |
| Previous Message | hubert depesz lubaczewski | 2010-04-23 21:40:35 | Re: Postgres stats collector showing high disk I/O |