| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Ram Pratap Maurya <ram(dot)maurya(at)lavainternational(dot)in>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Cc: | Manu Saxena <manu(dot)saxena(at)lavainternational(dot)in> |
| Subject: | Re: Huge archive log generate in Postgresql-13 |
| Date: | 2022-04-18 16:00:20 |
| Message-ID: | 5e94410e-ae0e-db88-24cc-58805a9f73d0@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Clive Swan | 2022-04-18 19:15:38 | Re: Huge archive log generate in Postgresql-13 |
| Previous Message | Holger Jakobs | 2022-04-18 12:10:08 | Re: Huge archive log generate in Postgresql-13 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2022-04-18 16:33:15 | Re: Facing issues with pgsql upgrade. |
| Previous Message | Achilleas Mantzios | 2022-04-18 14:17:12 | Re: What do you guys use for issue tracking, CI/CD and team management? any nice open source options? |