| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, SASIKUMAR Devaraj <sashikumard(at)yahoo(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: VacuumDB generating huge WAL filed |
| Date: | 2024-12-12 06:35:47 |
| Message-ID: | 52122541702b838b870bbd239008625aacc042dd.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, 2024-12-11 at 23:25 -0700, David G. Johnston wrote:
> On Wednesday, December 11, 2024, SASIKUMAR Devaraj <sashikumard(at)yahoo(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | SASIKUMAR Devaraj | 2024-12-12 12:27:44 | Re: VacuumDB generating huge WAL filed |
| Previous Message | David G. Johnston | 2024-12-12 06:25:52 | Re: VacuumDB generating huge WAL filed |