| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Darafei Komяpa Praliaskouski <me(at)komzpa(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Banck <mbanck(at)gmx(dot)net> |
| Subject: | Re: Berserk Autovacuum (let's save next Mandrill) |
| Date: | 2020-03-12 04:07:08 |
| Message-ID: | CAApHDvrti+FWNuox7UMWVkj1H1dmddh-Ri-v-myr+KCdwpkihQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 11 Mar 2020 at 17:24, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> On Wed, 2020-03-11 at 12:00 +0900, Masahiko Sawada wrote:
> > I might be missing your point but could you elaborate on that in what
> > kind of case you think this lead to unnecessary vacuums?
>
> If you have an insert-only table that has 100000 entries, it will get
> vacuumed roughly every 20000 new entries. The impact is probably too
> little to care, but it will increase the contention for the three
> autovacuum workers available by default.
I guess that depends on your definition of unnecessary. If you want
Index Only Scans, then those settings don't seem unreasonable. If you
want it just to reduce the chances or impact of an anti-wraparound
vacuum then likely it's a bit too often.
I understand this patch was born due to the anti-wraparound case, but
should we really just ignore the Index Only Scan case?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2020-03-12 04:17:36 | Re: BEFORE ROW triggers for partitioned tables |
| Previous Message | movead.li@highgo.ca | 2020-03-12 03:51:38 | A bug when use get_bit() function for a long bytea string |