From: | Ram Pratap Maurya <ram(dot)maurya(at)lavainternational(dot)in> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | RE: Huge archive log generate in Postgresql-13 |
Date: | 2022-04-22 03:41:41 |
Message-ID: | KL1PR0601MB4433F962EC723ADF96CC4604F0F79@KL1PR0601MB4433.apcprd06.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
Dear Adrian,
We are using "pg_log_archive" for Point-in-Time Recovery and DR replication.
Regards,
Ram Pratap.
-----Original Message-----
From: Adrian Klaver [mailto:adrian(dot)klaver(at)aklaver(dot)com]
Sent: 21 April 2022 21:35
To: Ram Pratap Maurya <ram(dot)maurya(at)lavainternational(dot)in>; pgsql-general(at)postgresql(dot)org
Subject: Re: Huge archive log generate in Postgresql-13
On 4/19/22 21:31, Ram Pratap Maurya wrote:
> Dear Adrian,
>
> We are using binary replication and par day *pg_log_archive* total
> size is increase after upgrade for PG11 to PG13.
So what is pruning the WAL's in pg_log_archive?
Or to put it another way what is the purpose of pg_log_archive and how is it managed?
>
> Regards,
>
> Ram Pratap.
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2022-04-22 07:49:34 | Re: Estimating HugePages Requirements? |
Previous Message | Adrian Klaver | 2022-04-21 16:04:55 | Re: Huge archive log generate in Postgresql-13 |
From | Date | Subject | |
---|---|---|---|
Next Message | Willy-Bas Loos | 2022-04-22 11:25:45 | logical replication worker can't find postgis function |
Previous Message | David G. Johnston | 2022-04-22 03:35:22 | Re: autovacuum_freeze_max_age on append-only tables |