public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ram Pratap Maurya <[email protected]>
To: Adrian Klaver <[email protected]>
To: [email protected] <[email protected]>
Subject: RE: Huge archive log generate in Postgresql-13
Date: Tue, 19 Apr 2022 04:41:44 +0000
Message-ID: <KL1PR0601MB44331424CA913E84AAEB9087F0F29@KL1PR0601MB4433.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <KL1PR0601MB443325E8306395D5428BAC04F0F29@KL1PR0601MB4433.apcprd06.prod.outlook.com>
References: <KL1PR0601MB4433D6A72DE1CA03D9D6F75DF0F39@KL1PR0601MB4433.apcprd06.prod.outlook.com>
<[email protected]>
<KL1PR0601MB443325E8306395D5428BAC04F0F29@KL1PR0601MB4433.apcprd06.prod.outlook.com>
Dear Adrian,
If we set parameter "PG-WAL = replica" in PG13 conf file , there is any issue in replication through PG_WAL and pg_log_archive log.
https://www.postgresql.org/docs/13/runtime-config-wal.html
Regards,
Ram Pratap.
-----Original Message-----
From: Ram Pratap Maurya
Sent: 19 April 2022 09:00
To: Adrian Klaver <[email protected]>; [email protected]
Cc: Manu Saxena <[email protected]>
Subject: RE: Huge archive log generate in Postgresql-13
Dear Adrian,
We have two replica system one is Slave and other id DR server .
Salve server replicate from PG_WAL and DR system replicate from pg_log_archive.
Can you please suggest what changes need to required in PG13 conf file.
Regards,
Ram Pratap.
-----Original Message-----
From: Adrian Klaver [mailto:[email protected]]
Sent: 18 April 2022 21:30
To: Ram Pratap Maurya <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>
Cc: Manu Saxena <[email protected]<mailto:[email protected]>>
Subject: Re: Huge archive log generate in Postgresql-13
On 4/18/22 04:34, Ram Pratap Maurya wrote:
> Hi Support,
>
> We have upgraded postgresql DB from version 11 to 13 . after upgrade
> to
> 13 huge archive log generate in system .
>
> Before upgrade per day 120GB to 150 GB log generated but after
> upgrade per day approx. 250 to 300 GB log generated.
Where are you measuring this in the WAL directory or the archive directory?
Do you have replication set up from this server and if so what type?
FYI, the wal_level setting of hot_standby is deprecated and maps to replica since version 9.6. At some point you might want to change to match current documentation.
>
> Can you please suggest why huge archive log generated after upgrade
> there any configure setting or this is Postgresql-13 behaviour.
>
> Postgresql-13 Postgresql conf file attached for your references.
>
> Regards,
>
> Ram Pratap.
>
--
Adrian Klaver
[email protected]<mailto:[email protected]>
Attachments:
[application/octet-stream] postgresql.conf (27.6K, 3-postgresql.conf)
download
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: <KL1PR0601MB44331424CA913E84AAEB9087F0F29@KL1PR0601MB4433.apcprd06.prod.outlook.com>
* 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