Re: autovacuum launcher using InitPostgres - Mailing list pgsql-hackers

From Tom Lane
Subject Re: autovacuum launcher using InitPostgres
Date
Msg-id 4129.1251736449@sss.pgh.pa.us
Whole thread Raw
In response to Re: autovacuum launcher using InitPostgres  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: autovacuum launcher using InitPostgres
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Tom Lane wrote:
>> I wonder if it would be cleaner to include the launcher in
>> the autovacuum_max_workers parameter, and increase the min/default
>> values of that by one.

> Huh, yeah, sorry about that -- fixed here.  I think the name of the
> param, which includes "worker", precludes from raising the values.

Well, I'm not sure the average user knows or cares about the difference
between the launcher and the workers.  The thing that was in the back of
my mind was that we would now have the option to have the launcher show
up in pg_stat_activity.  If we were to do that then the case for
counting it in the user-visible number-of-processes parameter would get
a lot stronger (enough to justify renaming the parameter, if you insist
that the launcher isn't a worker).  I don't however have any strong
opinion on whether we *should* include it in pg_stat_activity ---
comments?

In the meantime, this looks reasonably sane in a fast read-through,
but I saw a few comments that could use improvement, and I have not
tried to actually review it (like look for missed places to change).
Do you mind if I work it over for an hour or two?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: autovacuum launcher using InitPostgres
Next
From: "Kevin Grittner"
Date:
Subject: Re: Add YAML option to explain