From: John Scalia <jayknowsunix@gmail.com>
To: Raj kumar <rajkumar820999@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Wal keep segment
Date: Sat, 25 Apr 2020 08:14:59 -0400
Message-ID: <675BEC19-1A77-4DFC-88DB-42982FA6E922@gmail.com> (raw)
In-Reply-To: <CACxU--W3OcC85A65rypL+t+P_uMje0xdYXqgAzSdTEQuM41Qhg@mail.gmail.com>
References: <CACxU--W3OcC85A65rypL+t+P_uMje0xdYXqgAzSdTEQuM41Qhg@mail.gmail.com>
Wal_keep_segments is a MINIMUM setting value, meaning the database is guaranteed to keep at least that many WAL segments. If you have replication setup and it’s fallen behind or broken, then WAL segments can rapidly accumulate on a fairly busy server. I suspect without having your details that something of this nature is occurring.
—
Jay
Sent from my iPad
> On Apr 25, 2020, at 8:09 AM, Raj kumar <rajkumar820999@gmail.com> wrote:
>
>
> Hi,
>
> I have "wal_keep_segment" set as 256.
> But I could see that around 700 files are present inside pg_wal directory.
>
> I thought after reaching 256, wal writer will start overwriting from 1st.
>
> What is the upper limit of these number of wal files in the directory?
>
> Thanks and regards
> Raj kumar
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: jayknowsunix@gmail.com, rajkumar820999@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Wal keep segment
In-Reply-To: <675BEC19-1A77-4DFC-88DB-42982FA6E922@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