From: | dhanuj hippie <dhanuj(dot)hippie(at)gmail(dot)com> |
---|---|
To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_xlog keeps growing |
Date: | 2017-02-28 04:20:44 |
Message-ID: | CAGqAkKeyDpsXeWqdvyLy=5MOHAeAoupEJbdYPTsNxRXSrwh+aQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
So does it work like - it can go upto 16MB*1024 times which is 16GB, and
then this will be cleaned up automatically ?
On Tue, Feb 28, 2017 at 9:47 AM, dhanuj hippie <dhanuj(dot)hippie(at)gmail(dot)com>
wrote:
> psql (9.3.5)
> wal_keep_segments = 1024
>
> On Tue, Feb 28, 2017 at 9:16 AM, Rob Sargent <robjsargent(at)gmail(dot)com>
> wrote:
>
>>
>> > On Feb 27, 2017, at 8:33 PM, dhanuj hippie <dhanuj(dot)hippie(at)gmail(dot)com>
>> wrote:
>> >
>> > Hi,
>> >
>> > I have a postgres cluster running in hot_standby. I see the pg_xlog is
>> growing over time (may files of size 16 MB each). The replication lag is
>> very less ~2kB, and never goes into a bad state.
>> > I'm manually resetting this once a while using pg_resetxlog command.
>> > Is there a way to understand why my system keeps running into this
>> problem ?
>> >
>> > Thanks
>>
>> wal_keep_segments is set to ???
>>
>> (and version = ???, etc)
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-02-28 04:37:49 | Re: cpu hight sy% usage |
Previous Message | dhanuj hippie | 2017-02-28 04:17:13 | Re: pg_xlog keeps growing |