From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Olivier Gautherot <ogautherot(at)gautherot(dot)net>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Atul Kumar <akumar14871(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: autovacuum recommendations for Large tables |
Date: | 2020-11-18 12:07:10 |
Message-ID: | 75ca65304d1cb8a4288d1b78cf7adf067dbe354e.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 2020-11-17 at 22:17 +0100, Olivier Gautherot wrote:
> On Tue, Nov 17, 2020 at 12:05 AM David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> > On Mon, Nov 16, 2020 at 3:57 PM Atul Kumar <akumar14871(at)gmail(dot)com> wrote:
> > > I only have this one big table in the database of size 3113 GB with rows 7661353111.
> > >
> > > Right Now the autovacuum setting for that table is set to
> > > {autovacuum_enabled=true,autovacuum_vacuum_scale_factor=0.2,autovacuum_analyze_scale_factor=0.2}
> >
> > auto-vacuum doesn't care directly about absolute size, it cares about change (relative to absolute size in many cases, hence the scale factors).
> >
> > David J.
> >
>
> David is correct.
>
> If it helps, I put together a few thoughts and own experience on a blog:
> https://sites.google.com/gautherot.net/postgresql/vacuum
>
> Hope you find it useful.
Then I can chime in with https://www.cybertec-postgresql.com/en/tuning-autovacuum-postgresql/
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Leo Jin | 2020-11-18 13:44:10 | Re: Race condition with restore_command on streaming replica |
Previous Message | Laurenz Albe | 2020-11-18 12:02:25 | Re: vacuum vs vacuum full |