From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
---|---|
To: | Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: further bootstrap cleanup |
Date: | 2007-02-19 14:39:45 |
Message-ID: | 45D9B6B1.6040100@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Alvaro Herrera wrote:
> Heikki Linnakangas wrote:
>> Alvaro Herrera wrote:
>>> Here is a patch further cleaning up dummy process startup and the
>>> bootstrap code itself a little.
>> Could we please call the "dummy" processes something else? Dummy
>> seems a bit belittling for such important things like bgwriter and the
>> startup process.
>>
>> How about worker or helper process?
>
> Well, sure, but the name was there before I patched it :-) This is
> mostly a code issue though, not something that shows up at all at the
> user level.
Yeah. I thought now would be a good time to change since you're messing
with the code anyway.
I'd be happy with something like "system process" that carries the
meaning of something that's internal and important. But "system process"
makes me think of the operating system.
Non-backend process would be a nice contrast to normal backend
processes, but a negated word like that is awkward.
Internal process?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-02-19 15:33:36 | Re: WIP patch - INSERT-able log statements |
Previous Message | Guillaume Smet | 2007-02-19 14:39:02 | Re: WIP patch - INSERT-able log statements |