public inbox for [email protected]
help / color / mirror / Atom feedFrom: SASIKUMAR Devaraj <[email protected]>
To: vignesh kumar <[email protected]>
To: Pgsql-admin <[email protected]>
Subject: Re: VacuumDB generating huge WAL filed
Date: Fri, 13 Dec 2024 10:03:51 +0000 (UTC)
Message-ID: <[email protected]> (raw)
In-Reply-To: <MN0PR20MB49129306EE76C40E778EE7A5873F2@MN0PR20MB4912.namprd20.prod.outlook.com>
References: <[email protected]>
<[email protected]>
<MN0PR20MB49129306EE76C40E778EE7A5873F2@MN0PR20MB4912.namprd20.prod.outlook.com>
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?
Sent from Yahoo Mail for iPhone
On Thursday, December 12, 2024, 8:37 PM, vignesh kumar <[email protected]> wrote:
Check for the max walsize allocated in postgresql.conf and also check on checkpoint completion target default is 0.9 this says how frequent the checkpoint can be applied that adds to wal lan generation.
First do a table level vaccuum and see what's causing it to write more wal files.
Sent from Outlook for AndroidFrom: SASIKUMAR Devaraj <[email protected]>
Sent: Thursday, December 12, 2024 11:38:26 AM
To: Pgsql-admin <[email protected]>
Subject: VacuumDB generating huge WAL filed Hi All
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?
RegardsSasi
Sent from Yahoo Mail for iPhone
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]
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