From: | Andy Chambers <achambers(at)mcna(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Do I need archive_mode = on for hot standby? |
Date: | 2012-07-10 22:26:05 |
Message-ID: | CAAfW55r-5=Wk-VEXkMJXsWtPrLZueZkfgV+9xZNPviqsj=jixw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jul 2, 2012 at 3:33 AM, Janne H <jannehson51(at)yahoo(dot)com> wrote:
> Hi there.
>
> I'm planning on setting up a master database and multiple hot standby
> slaves using streaming replication.
>
> If I use a large(*) value on
> wal_keep_segments
> do I really need archive_mode = on then?
>
> Any potential problems with this strategy I should be aware about?
>
> (*) With large value I mean a value such that a failed slave will be up
> and running again (with a few days margin) before the master server starts
> to clean out old WAL segments.
>
I believe you are correct. At least that's what it says here...
http://wiki.postgresql.org/wiki/Streaming_Replication
--
Andy
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-07-10 22:48:11 | Re: Sequence moves forward when failover is triggerred |
Previous Message | Andy Chambers | 2012-07-10 22:17:23 | Sequence moves forward when failover is triggerred |