| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Markus Wanner <markus(at)bluegap(dot)ch>, kaigai(at)kaigai(dot)gr(dot)jp, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Review: Extra Daemons / bgworker |
| Date: | 2012-12-03 15:44:46 |
| Message-ID: | 20121203154445.GF5276@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs wrote:
> On 3 December 2012 15:17, Markus Wanner <markus(at)bluegap(dot)ch> wrote:
> > The only process that currently starts background workers ... ehm ...
> > autovacuum workers is the autovacuum launcher. It uses the above
> > Postmaster Signal in autovacuum.c:do_start_autovacuum_worker() to have
> > the postmaster launch bg/autovac workers on demand.
>
> My understanding was that the patch keep autovac workers and
> background workers separate at this point.
That is correct.
> Is there anything to be gained *now* from merging those two concepts?
> I saw that as refactoring that can occur once we are happy it should
> take place, but isn't necessary.
IMO it's a net loss in robustness of the autovac implementation.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Wanner | 2012-12-03 15:51:22 | Re: Review: Extra Daemons / bgworker |
| Previous Message | Alvaro Herrera | 2012-12-03 15:43:21 | Re: Review: Extra Daemons / bgworker |