From: | Toby Corkindale <toby(dot)corkindale(at)strategicdata(dot)com(dot)au> |
---|---|
To: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: repmgr and archive_mode |
Date: | 2011-07-30 06:57:06 |
Message-ID: | 342774324.4323.1312009026905.JavaMail.root@dmz03 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
----- Original Message -----
> <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
Aaah.. now that explains it perfectly.
Many thanks for clearing that up! I hadn't realised that you could only change one of the two options on the fly.
Thanks,
Toby
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2011-07-30 08:06:03 | Re: Factors Influencing Participant Satisfaction with Free/Libre and Open Source Software Projects |
Previous Message | Jaime Casanova | 2011-07-30 05:28:36 | Re: repmgr and archive_mode |