Feedback-ID: ia2694551:Fastmail
Date: Tue, 27 Feb 2024 19:22:17 +0100
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Scott Ribe <scott_ribe@elevated-dev.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: explosive WAL growth
Message-ID: <202402271822.t4vbqds7mjge@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <C7733827-4E85-47AF-8D39-349D007E229A@elevated-dev.com>
Archived-At: 
 <https://www.postgresql.org/message-id/202402271822.t4vbqds7mjge%40alvherre.pgsql>
Precedence: bulk

On 2024-Feb-27, Scott Ribe 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.

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.

Some backup tools implement parallel archiving of WAL files, which helps
you deal with massive accumulation of them.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/