From: | Mohan NBSPS <mohan(dot)nbs(dot)ont(at)gmail(dot)com> |
---|---|
To: | Muhammad Imtiaz <imtiaz(dot)m(at)bitnine(dot)net> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: postgrsql 9.5: Old WAL files remain in secondary `pg_xlog` |
Date: | 2024-06-05 00:08:10 |
Message-ID: | CAPCvfWfBR_DmPafxLDBvXhGLmP-+8w-2t27FykDuC=ByG0f6Fw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
thank you.
the replication seems to work.
sorry, my question was incomplete.
I see few very old (over 2 years) WAL files remain in the secondary
(primary is clean with only
new WAL files).
On Fri, May 31, 2024 at 11:58 PM Muhammad Imtiaz <imtiaz(dot)m(at)bitnine(dot)net>
wrote:
> Hi ,
>
> Ensure the following:
>
> • Replication is functioning correctly between the primary and secondary
> servers, with no lag.
>
> • The archive_command parameter is properly configured in the database
> settings.
>
> Regards,
>
> Muhammad Imtiaz
>
> On Sat, 1 Jun 2024, 04:01 Mohan NBSPS, <mohan(dot)nbs(dot)ont(at)gmail(dot)com> wrote:
>
>> Hello Community,
>>
>> Although the WAL retaining settings are default (max size 1GB),
>> `wal_keep_segments` is 25, checkpoint target is 2.5 minutes(default).
>> I noticed a few WAL files in secondary nodes (streaming replication)
>> `pg_xlog`
>> folder.
>>
>> What could be the reason why postgresql did not delete these ?
>>
>> Thank you
>> Regards
>> Mohan
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Mohan NBSPS | 2024-06-05 00:08:32 | Re: postgrsql 9.5: Old WAL files remain in secondary `pg_xlog` |
Previous Message | Teja Jakkidi | 2024-06-04 18:30:32 | Re: pg_dump and restore without indexes |