Re: setting high value for wal_keep_segments

From: AI Rumman <rummandba(at)gmail(dot)com>
To: bricklen <bricklen(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 16:00:35
Message-ID: CAGoODpccHUfWPdJYEbP5K9eKJSPM_EoGUnbfqiPETsSWc8etdw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Yeah, I already set it like that and it works.
Thanks.

On Thu, Aug 8, 2013 at 11:59 AM, bricklen <bricklen(at)gmail(dot)com> wrote:

> 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.
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Grittner 2013-08-08 18:18:22 Re: How to avoid Force Autovacuum
Previous Message bricklen 2013-08-08 15:59:05 Re: setting high value for wal_keep_segments