Dear Holger,

we have one slave server and one DR server.

salve server working on streaming replication and DR server replicate with Archive log.

if we change  "wal_level " parameter value to  “replica” there any impact in existing server (Salve and DR) replication?

Please suggest .

Regards,

Ram Pratap.

From: Ram Pratap Maurya
Sent: 21 April 2022 09:49
To: Ram Pratap Maurya <[email protected]>
Subject: FW: Huge archive log generate in Postgresql-13

---------- Forwarded message ---------
From: Clive Swan <[email protected]>
Date: Tue, Apr 19, 2022 at 12:45 AM
Subject: Re: Huge archive log generate in Postgresql-13
To: Holger Jakobs <[email protected]>, [email protected] <[email protected]>

Grenting,

Is your logging set to high verbosity??

Usually use high verbosity for debugging, then change to low verbosity. 

Clive

---

From: Holger Jakobs <[email protected]>
Sent: Monday, 18 April 2022, 13:10
To: [email protected] <[email protected]>
Subject: Re: Huge archive log generate in Postgresql-13

wal_level = hot_standby            # minimal, replica, or logical
                    # (change requires restart)

Set wal_level to one of the allowed values. It's possible that your value gets interpreted as logical, thus creating larger wal entries.

Am 18.04.22 um 13:47 schrieb Ram Pratap Maurya:

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.

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.

-- 
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012