| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | David Gould <daveg(at)sonic(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com> |
| Subject: | Re: BUG #13750: Autovacuum slows down with large numbers of tables. More workers makes it slower. |
| Date: | 2016-03-18 22:13:17 |
| Message-ID: | 20160318221317.GA182976@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
David Gould wrote:
> I have some thoughts for a different approach. In short, the stats collector
> actually knows what needs vacuuming because queries that create dead tuples
> tell it. I'm considering have the stats collector maintain a queue of
> vacuum work and that autovacuum request work from the stats collector. When I
> have something more concrete I'll post it on hackers.
Hm, ideally we would have something backpatchable, but this new idea
doesn't sound so to me. I think that having some variant of the patch
you proposed previously would be better for the stable branches.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2016-03-18 22:17:25 | Re: BUG #13750: Autovacuum slows down with large numbers of tables. More workers makes it slower. |
| Previous Message | Vik Fearing | 2016-03-18 22:08:46 | Re: BUG #14027: n_tup_ins increments regardless of insertion success |