Postgres Pro
Downloads
Home   >   mailing lists

Re: Huge archive log generate in Postgresql-13 - Mailing list pgsql-admin

From Clive Swan
Subject Re: Huge archive log generate in Postgresql-13
Date
Msg-id CWXP123MB3959D7C4AB99BE0D1D6F38F4A0F39@CWXP123MB3959.GBRP123.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Huge archive log generate in Postgresql-13  (Holger Jakobs <holger@jakobs.com>)
List pgsql-admin
Tree view
Grenting,
Is your logging set to high verbosity??

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

Clive

From: Holger Jakobs <holger@jakobs.com>
Sent: Monday, 18 April 2022, 13:10
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
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

pgsql-admin by date:

Previous
From: Holger Jakobs
Date:
Subject: Re: Huge archive log generate in Postgresql-13
Next
From: Kristjan Mustkivi
Date:
Subject: Pgbouncer, docker and systemd