public inbox for [email protected]  
help / color / mirror / Atom feed
From: SASIKUMAR Devaraj <[email protected]>
To: Laurenz Albe <[email protected]>
To: David G. Johnston <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: VacuumDB generating huge WAL filed
Date: Thu, 12 Dec 2024 12:27:44 +0000 (UTC)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<CAKFQuway7Ly58D_e8UBaDR4hCw9T-2yvWiJ3+EZNzbvXoRWjMQ@mail.gmail.com>
	<[email protected]>

Hi
Since it is generating 60GB in few mins, my replication lag is increasing upto 10Gb for around 10 mins, which may seen as possible data loss in case of primary node failure 
RegardsSasi


Sent from Yahoo Mail for iPhone


On Thursday, December 12, 2024, 12:06 PM, Laurenz Albe <[email protected]> wrote:

On Wed, 2024-12-11 at 23:25 -0700, David G. Johnston wrote:
> On Wednesday, December 11, 2024, SASIKUMAR Devaraj <[email protected]> wrote:
> > When we are running vacuumdb for our database of 1.5TB it is generating approximately 60GB
> > of WAL files? Any way we can reduce this WAL file generation?
> 
> Set a much more aggressive autovacuum so you don’t accumulate as much dead tuples between runs?

You can also activate "wal_compression" for smaller full-page images
and increase "max_wal_size" to get fewer of them.

But 60GB of WAL shouldn't be a problem.  Why are they a problem for you?

Yours,
Laurenz Albe







view thread (7+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: VacuumDB generating huge WAL filed
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox