|
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----- 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:adrian.klaver@xxxxxxxxxxx] Sent: 18 April 2022 21:30 To: Ram Pratap Maurya <ram.maurya@xxxxxxxxxxxxxxxxxxxx>;
pgsql-general@xxxxxxxxxxxxxx Cc: Manu Saxena <manu.saxena@xxxxxxxxxxxxxxxxxxxx> 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 |
Attachment:
postgresql.conf
Description: postgresql.conf
