Message-ID: <5e94410e-ae0e-db88-24cc-58805a9f73d0@aklaver.com>
Date: Mon, 18 Apr 2022 09:00:20 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.8.0
Subject: Re: Huge archive log generate in Postgresql-13
Content-Language: en-US
To: Ram Pratap Maurya <ram.maurya@lavainternational.in>,
 "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Cc: Manu Saxena <manu.saxena@lavainternational.in>
References: 
 <KL1PR0601MB4433D6A72DE1CA03D9D6F75DF0F39@KL1PR0601MB4433.apcprd06.prod.outlook.com>
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: 
 <KL1PR0601MB4433D6A72DE1CA03D9D6F75DF0F39@KL1PR0601MB4433.apcprd06.prod.outlook.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/5e94410e-ae0e-db88-24cc-58805a9f73d0%40aklaver.com>
Precedence: bulk

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
adrian.klaver@aklaver.com