From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
---|---|
To: | Toby Corkindale <toby(dot)corkindale(at)strategicdata(dot)com(dot)au> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: repmgr and archive_mode |
Date: | 2011-07-30 05:28:36 |
Message-ID: | CAJKUy5h3KVbVCvsuozic20mEOYtcoO28o-QmHtx61XAHkMV6xQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Jul 29, 2011 at 3:12 AM, Toby Corkindale
<toby(dot)corkindale(at)strategicdata(dot)com(dot)au> wrote:
> Hi,
> In the repmgr README, it suggests configuration should include:
>
> archive_mode = on
> archive_command = 'cd .'
>
> Could someone explain why we need archive_mode enabled? In my own testing of
> Pg's streaming replication, I've found it to work without this enabled.
>
it's not really needed but in some situations you could want to
archive wal segments (for example if you want to shut down the standby
without having to put a really big value in wal_keep_segments) and
while archive_command can be changed at anytime just reloading
archive_mode needs to restart the server. so this is just a good
configuration for 24x7 setups
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
From | Date | Subject | |
---|---|---|---|
Next Message | Toby Corkindale | 2011-07-30 06:57:06 | Re: repmgr and archive_mode |
Previous Message | bricklen | 2011-07-29 22:45:59 | Finding referecing and referenced tables, adaptation from David Fetter's solution |