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?
On Thursday, December 12, 2024, 8:37 PM, vignesh kumar <vigneshkumar.venugopal@outlook.com> 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.
From: SASIKUMAR Devaraj <sashikumard@yahoo.com>
Sent: Thursday, December 12, 2024 11:38:26 AM
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
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?
Regards
