| 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> |
| Subject: | Re: Huge archive log generate in Postgresql-13 |
| Date: | 2022-04-21 16:04:55 |
| Message-ID: | 87593cae-6123-05dc-344a-23e3ffca7a4e@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
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 | Ram Pratap Maurya | 2022-04-22 03:41:41 | RE: Huge archive log generate in Postgresql-13 |
| Previous Message | Ram Pratap Maurya | 2022-04-21 05:54:29 | RE: Huge archive log generate in Postgresql-13 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Lewis | 2022-04-21 18:12:12 | Re: LwLocks contention |
| Previous Message | Adrian Klaver | 2022-04-21 14:46:39 | Re: PostgreSQL 10.20 crashes / Antivirus |