public inbox for [email protected]  

help / color / mirror / Atom feed

From: Adrian Klaver <[email protected]>
To: Ram Pratap Maurya <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: Huge archive log generate in Postgresql-13
Date: Thu, 21 Apr 2022 09:04:55 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <KL1PR0601MB44332854BD7B97CC9D266135F0F59@KL1PR0601MB4433.apcprd06.prod.outlook.com>
References: <KL1PR0601MB4433D6A72DE1CA03D9D6F75DF0F39@KL1PR0601MB4433.apcprd06.prod.outlook.com>
	<[email protected]>
	<KL1PR0601MB443325E8306395D5428BAC04F0F29@KL1PR0601MB4433.apcprd06.prod.outlook.com>
	<KL1PR0601MB44331424CA913E84AAEB9087F0F29@KL1PR0601MB4433.apcprd06.prod.outlook.com>
	<[email protected]>
	<KL1PR0601MB44332854BD7B97CC9D266135F0F59@KL1PR0601MB4433.apcprd06.prod.outlook.com>

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
[email protected]

view thread (17+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Huge archive log generate in Postgresql-13
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox