| From: | Karthik Yellapragada <karthik(dot)yellapragada(at)gmail(dot)com> |
|---|---|
| To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: explosive WAL growth |
| Date: | 2024-02-27 18:58:05 |
| Message-ID: | CACXtxt8X=UkJvdawDuaaOFmPeKQcNnzFgH7xuf=FYOvCstup3Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Just out of curiosity, what was the job doing?
On Tue, Feb 27, 2024 at 10:49 AM Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
wrote:
> Found it. Kubernetes cronjob task.
>
> > On Feb 27, 2024, at 11:22 AM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
> wrote:
> >
> > It could be autovacuum processing large tables that haven't been
> > processed in a long time, in emergency mode. This happens if you turn
> > it off and do nothing to substitute it.
>
> We have autovacuum on, and pretty well tuned.
>
> > Some backup tools implement parallel archiving of WAL files, which helps
> > you deal with massive accumulation of them.
>
> We'll get that in an upgrade we're getting ready to deploy. Ironically, it
> might have just hidden this problem ;-)
>
> --
Thanks & Regards
Karthik Yellapragada
+1 860 830 5235
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2024-02-27 19:19:25 | Re: explosive WAL growth |
| Previous Message | Scott Ribe | 2024-02-27 18:48:34 | Re: explosive WAL growth |