Re: Old WAL files under pg_xlog not getting delete

From: rammohan ganapavarapu <rammohanganap(at)gmail(dot)com>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Old WAL files under pg_xlog not getting delete
Date: 2019-01-31 16:22:12
Message-ID: CALm_Vji8606+5bcqDHBfpwAoft532fyM3YH_XSkGQHhD+0KPWA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Ron,

I have changed the wal_keep_segments=100 and restarted the postgresql
processes but i still see 500+ files under pg_xlog, i had to run checkpoint
manually to clean.

Ram

On Wed, Jan 30, 2019 at 7:19 PM Ron <ronljohnsonjr(at)gmail(dot)com> wrote:

> On 1/30/19 9:09 PM, rammohan ganapavarapu wrote:
>
> Thank you all, but irrespective of count i have why is it keeping old
> files?
>
>
> Because you're telling it to!!
>
> max_wal_size= 1GB
> wal_keep_segments=500
>
> and how is it using those files? Is there any processes that can flush or
> remove those files?
>
>
> Change the parameter and restart the server...
>
>
> On Wed, Jan 30, 2019, 4:11 PM David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com wrote:
>
>> On Wed, Jan 30, 2019 at 5:00 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
>> wrote:
>> > Hmm ... I would recommend to keep the xlog files in a subdir, not the
>> > root of the filesystem.
>>
>> They are in a subdir (under /opt/pgdata), and the OP seems likely to
>> have omitted the self/parent hidden directories during his check as
>> well. Plus per the docs we actually expect 501 so there isn't a need
>> to account for 6 extra, just 5.
>>
>> Dave
>>
>>
> --
> Angular momentum makes the world go 'round.
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message John Scalia 2019-01-31 16:37:19 Re: Old WAL files under pg_xlog not getting delete
Previous Message watcher 2019-01-31 08:55:42 error xmin from before relfrozenxid