From: | Lucio Chiessi <lucio(dot)chiessi(at)trustly(dot)com> |
---|---|
To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: explosive WAL growth |
Date: | 2024-02-27 18:22:18 |
Message-ID: | CADoTbHX+1ZjOm6iqUkW+Aaf6Etq8c_+z6b+XeagyS_QTHv3-Fw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Has any autovacuum, vacuum, or reindex occurred?
These operations generate lots of WAL depending on the size of the data
related.
*Lucio Chiessi*
Senior Database Administrator
Trustly, Inc.
M: +55 27 996360276
<https://www.linkedin.com/company/trustly/>
<https://www.facebook.com/trustly> <https://twitter.com/Trustly>
<https://www.linkedin.com/company/trustly/>
<https://www.facebook.com/trustly> <https://twitter.com/Trustly>
On Tue, Feb 27, 2024 at 3:10 PM Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
wrote:
> Something is causing our WAL to grow 160GB/hour *faster* than archiving.
> (Archiving appears to be working normally.) This started in the past couple
> of days.
>
> I am having some trouble finding the cause of this. I am looking at
> pg_stat_statements, # calls, time, shared blocks written. I am also looking
> at recent client app deployments.
>
> My next step might be to use something like pg_waldump to see what's in
> this WAL.
>
> Any suggestions?
>
> --
> Scott Ribe
> scott_ribe(at)elevated-dev(dot)com
> https://www.linkedin.com/in/scottribe/
>
>
>
>
>
>
--
Please read our privacy policy here
<https://www.trustly.net/about-us/privacy-policy> on how we process your
personal data in accordance with the General Data Protection Regulation
(EU) 2016/679 (the “GDPR”) and other applicable data protection legislation.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2024-02-27 18:48:34 | Re: explosive WAL growth |
Previous Message | Alvaro Herrera | 2024-02-27 18:22:17 | Re: explosive WAL growth |