pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Old WAL files under pg_xlog not getting delete
Date: Wed, 30 Jan 2019 17:37:25 -0600
Message-ID: <aea0796a-9b55-aa75-4ad3-5377fc03e240@gmail.com> (raw)
In-Reply-To: <CAKFQuwYdq2Pu-Bwmq-Up+suKyoD3hRdOKhOSU16oYAqHmPOAbg@mail.gmail.com>
References: <CALm_Vjjjti+z6m+svMGfoeiLhyjnNxCksT4RucSWVr7G=rKAmQ@mail.gmail.com>
	<CAKFQuwYdq2Pu-Bwmq-Up+suKyoD3hRdOKhOSU16oYAqHmPOAbg@mail.gmail.com>



On 1/30/19 5:10 PM, David G. Johnston wrote:
> On Wed, Jan 30, 2019 at 3:58 PM rammohan ganapavarapu
> <rammohanganap@gmail.com> wrote:
>> I am trying to understand why postgresql not removing WAL logs under pg_xlog in 9.6, below are my settings
>>
>> wal_keep_segments=500
>>
>> pg_xlog/|wc -l
>> 506
> You told PostgreSQL to keep 500 files and it has (the number kept
> apparently fluctuates a little bit).
>
> https://www.postgresql.org/docs/11/wal-configuration.html

Plus the ".", ".." and archive_status directories, and lost+found if pg_xlog 
is it's own partition.  That's four of the unknown six.  Add a .backup file 
or two and all 506 files are accounted for.

-- 
Angular momentum makes the world go 'round.




view thread (17+ messages)  latest in thread

Message-ID: <aea0796a-9b55-aa75-4ad3-5377fc03e240@gmail.com>
Permalink:  ../aea0796a-9b55-aa75-4ad3-5377fc03e240@gmail.com/
Also on:    postgresql.org/message-id/aea0796a-9b55-aa75-4ad3-5377fc03e240@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Old WAL files under pg_xlog not getting delete
  In-Reply-To: <aea0796a-9b55-aa75-4ad3-5377fc03e240@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox