From: | Don Seiler <don(at)seiler(dot)us> |
---|---|
To: | Raj kumar <rajkumar820999(at)gmail(dot)com> |
Cc: | John Scalia <jayknowsunix(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Wal keep segment |
Date: | 2020-04-25 13:28:55 |
Message-ID: | CAHJZqBCHyz=782zFLdvmHuSPEOiq0Va0C=yAx3fCYktLWWFPAA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Sat, Apr 25, 2020, 08:13 Raj kumar <rajkumar820999(at)gmail(dot)com> wrote:
> Hi John,
>
> Thank you.
>
> On Sat, 25 Apr 2020, 17:45 John Scalia, <jayknowsunix(at)gmail(dot)com> wrote:
>
>> 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(at)gmail(dot)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
>>
>
I would also see if you have a replication slot in use, and verify that it
actually should be in use.
Don.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Luis Marin | 2020-04-25 17:10:37 | Configuring Replication in Windows 2016 using Postgresql 9.x |
Previous Message | Raj kumar | 2020-04-25 13:13:18 | Re: Wal keep segment |