From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: explosive WAL growth
Date: Tue, 27 Feb 2024 11:48:34 -0700
Message-ID: <1334AE42-2DBF-4DA5-8F7B-529013796F55@elevated-dev.com> (raw)
In-Reply-To: <202402271822.t4vbqds7mjge@alvherre.pgsql>
References: <202402271822.t4vbqds7mjge@alvherre.pgsql>
Found it. Kubernetes cronjob task.
> On Feb 27, 2024, at 11:22 AM, Alvaro Herrera <alvherre@alvh.no-ip.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 ;-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, alvherre@alvh.no-ip.org, pgsql-admin@lists.postgresql.org
Subject: Re: explosive WAL growth
In-Reply-To: <1334AE42-2DBF-4DA5-8F7B-529013796F55@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox