Message-ID: <4c4820935c4be3f3df4a9b18258b459b12145b94.camel@cybertec.at>
Subject: Re: VacuumDB generating huge WAL filed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: SASIKUMAR Devaraj <sashikumard@yahoo.com>, vignesh kumar
	 <vigneshkumar.venugopal@outlook.com>, Pgsql-admin
	 <pgsql-admin@lists.postgresql.org>
Date: Fri, 13 Dec 2024 11:12:28 +0100
In-Reply-To: <1727122332.1852194.1734084231873@mail.yahoo.com>
References: <155477463.1496353.1733983706261.ref@mail.yahoo.com>
	 <155477463.1496353.1733983706261@mail.yahoo.com>
	 <MN0PR20MB49129306EE76C40E778EE7A5873F2@MN0PR20MB4912.namprd20.prod.outlook.com>
	 <1727122332.1852194.1734084231873@mail.yahoo.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.54.2 (3.54.2-1.fc41) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/4c4820935c4be3f3df4a9b18258b459b12145b94.camel%40cybertec.at>
Precedence: bulk

On Fri, 2024-12-13 at 10:03 +0000, SASIKUMAR Devaraj 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?
>
> We were able to identify the table generating around 40GB in
> few mins by vaccum process. It is partition table with dead
> tuple less than 0.5 percent. What may be next steps?

I think I told you: increase "max_wal_size" and enable "wal_compression".
That should reduce the amount of WAL.

Yours,
Laurenz Albe