Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: John Scalia <jayknowsunix@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Wal keep segment
Date: Sat, 25 Apr 2020 08:14:59 -0400
Message-Id: <675BEC19-1A77-4DFC-88DB-42982FA6E922@gmail.com>
References: 
 <CACxU--W3OcC85A65rypL+t+P_uMje0xdYXqgAzSdTEQuM41Qhg@mail.gmail.com>
Cc: pgsql-admin@lists.postgresql.org
In-Reply-To: 
 <CACxU--W3OcC85A65rypL+t+P_uMje0xdYXqgAzSdTEQuM41Qhg@mail.gmail.com>
To: Raj kumar <rajkumar820999@gmail.com>
Precedence: bulk

Wal_keep_segments is a MINIMUM setting value, meaning the database is guaran=
teed to keep at least that many WAL segments. If you have replication setup a=
nd it=E2=80=99s fallen behind or broken, then WAL segments can rapidly accum=
ulate on a fairly busy server. I suspect without having your details that so=
mething of this nature is occurring.
=E2=80=94
Jay

Sent from my iPad

> On Apr 25, 2020, at 8:09 AM, Raj kumar <rajkumar820999@gmail.com> wrote:
>=20
> =EF=BB=BF
> Hi,
>=20
> I have "wal_keep_segment" set as 256.
> But I could see that around 700 files are present inside pg_wal directory.=

>=20
> I thought after reaching 256, wal writer will start overwriting from 1st.
>=20
> What is the upper limit of these number of wal files in the directory?
>=20
> Thanks and regards
> Raj kumar