| From: | SASIKUMAR Devaraj <sashikumard(at)yahoo(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: VacuumDB generating huge WAL filed |
| Date: | 2024-12-12 12:27:44 |
| Message-ID: | 2060427903.1621547.1734006464981@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi
Since it is generating 60GB in few mins, my replication lag is increasing upto 10Gb for around 10 mins, which may seen as possible data loss in case of primary node failure
RegardsSasi
Sent from Yahoo Mail for iPhone
On Thursday, December 12, 2024, 12:06 PM, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
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 | Narendran .j | 2024-12-12 13:31:28 | Psql not working |
| Previous Message | Laurenz Albe | 2024-12-12 06:35:47 | Re: VacuumDB generating huge WAL filed |