From: | bricklen <bricklen(at)gmail(dot)com> |
---|---|
To: | AI Rumman <rummandba(at)gmail(dot)com> |
Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: setting high value for wal_keep_segments |
Date: | 2013-08-08 15:59:05 |
Message-ID: | CAGrpgQ_GyX=6YB7jc3YgXTbc2fNp8T-H4GTjTuHzkJp1M2tASg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Aug 8, 2013 at 6:23 AM, AI Rumman <rummandba(at)gmail(dot)com> wrote:
> Hi,
>
> I am going to sync slave with my master which is almost 500 G. I am not
> using archive directory instead of I am using wal files for streaming. As
> it may take almost 3 hours, I am thinking of setting up 400 for
> wal_keep_segments where I have enough space available.
>
> Without the space issue, could there be any other problem in setting up
> such high value for "wal_keep_segments"? As this is production, I need to
> confirmed.
>
Another data point: I set up SR on two systems recently in production with
the wal_keep_segments set to 10000 (lots of logs were being generated), and
the slaves were about 1TB each. No problems were experienced.
From | Date | Subject | |
---|---|---|---|
Next Message | AI Rumman | 2013-08-08 16:00:35 | Re: setting high value for wal_keep_segments |
Previous Message | dafNi zaf | 2013-08-08 15:33:15 | Re: DB transactions when browser freezes |