RE: Huge archive log generate in Postgresql-13 - Mailing list pgsql-general

From Ram Pratap Maurya
Subject RE: Huge archive log generate in Postgresql-13
Date
Msg-id KL1PR0601MB4433F962EC723ADF96CC4604F0F79@KL1PR0601MB4433.apcprd06.prod.outlook.com
Whole thread Raw
In response to Re: Huge archive log generate in Postgresql-13  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
Dear Adrian,

We are using  "pg_log_archive" for Point-in-Time Recovery and DR replication.


Regards,
Ram Pratap.

-----Original Message-----
From: Adrian Klaver [mailto:adrian.klaver@aklaver.com] 
Sent: 21 April 2022 21:35
To: Ram Pratap Maurya <ram.maurya@lavainternational.in>; pgsql-general@postgresql.org
Subject: Re: Huge archive log generate in Postgresql-13

On 4/19/22 21:31, Ram Pratap Maurya wrote:
> Dear Adrian,
> 
> We are using binary replication and par day *pg_log_archive* total 
> size is increase after upgrade for PG11 to PG13.

So what is pruning the WAL's in pg_log_archive?

Or to put it another way what is the purpose of pg_log_archive and how is it managed?

> 
> Regards,
> 
> Ram Pratap.
> 



--
Adrian Klaver
adrian.klaver@aklaver.com

pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: autovacuum_freeze_max_age on append-only tables
Next
From: Willy-Bas Loos
Date:
Subject: logical replication worker can't find postgis function