| From: | "Athanasios | ZenGuard" <athanasios(at)zenguard(dot)org> |
|---|---|
| To: | Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com> |
| Cc: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: Master-slave failover question |
| Date: | 2014-01-03 16:10:43 |
| Message-ID: | CAHPc5uRJNXBmo=+KtLeWimTm+KZiAkMCb1JjxYN4eRd_-BDz-g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Any sane values to it? This is what I am using right now (10 just to be on
the safe side, the 5000 (!) is a repmgr requirement(!))
max_wal_senders = 10 # max number of walsender processes
wal_keep_segments = 5000 # in logfile segments, 16MB each; 0 disables
On Fri, Jan 3, 2014 at 5:07 PM, Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com>wrote:
> If you are only relying on streaming replication (and not using archive
> shipping/hybrid replication), the probablity of 'catching-up' is as high as
> your wal_keep_segment.
>
> Regards
> Sameer
>
> PS: Sent from my Mobile device. Pls ignore typo n abb
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sameer Kumar | 2014-01-03 16:16:04 | Re: Master-slave failover question |
| Previous Message | Sameer Kumar | 2014-01-03 16:07:01 | Re: Master-slave failover question |