| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | SASIKUMAR Devaraj <sashikumard(at)yahoo(dot)com>, vignesh kumar <vigneshkumar(dot)venugopal(at)outlook(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: VacuumDB generating huge WAL filed |
| Date: | 2024-12-13 10:12:28 |
| Message-ID: | 4c4820935c4be3f3df4a9b18258b459b12145b94.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | kamal deen | 2024-12-13 16:27:43 | Postgres DB crashing in OpenSSL 3.2 Version |
| Previous Message | SASIKUMAR Devaraj | 2024-12-13 10:03:51 | Re: VacuumDB generating huge WAL filed |