Re: Old WAL files under pg_xlog not getting delete

"i had to run checkpoint manually to clean."

I see no problem with that.  Postgres would have checkpointed sooner or later.

On 1/31/19 10:22 AM, rammohan ganapavarapu wrote:
> 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
> <mailto: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 <mailto: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 <mailto: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.