Re: CLOG extension

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: CLOG extension
Дата
Msg-id 1336080282-sup-9116@alvh.no-ip.org
обсуждение исходный текст
Ответ на Re: CLOG extension  (Daniel Farina <daniel@heroku.com>)
Ответы Re: CLOG extension  (Daniel Farina <daniel@heroku.com>)
Re: CLOG extension  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Excerpts from Daniel Farina's message of jue may 03 17:04:03 -0400 2012:
> On Thu, May 3, 2012 at 1:56 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> > Possibly.  I have some fear of ending up with too many background
> > processes, but we may need them.
>
> I sort of care about this, but only on systems that are not very busy
> and could otherwise get by with fewer resources -- for example, it'd
> be nice to turn off autovacuum and the stat collector if it really
> doesn't have to be around.  Perhaps a Nap Commander[0] process or
> procedure (if baked into postmaster, to optimize to one process from
> two) would do the trick?

I'm not sure I see the point in worrying about this at all.  I mean, a
process doing nothing does not waste much resources, does it?  Other
than keeping a PID that you can't use for other stuff.

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Advisory locks seem rather broken
Следующее
От: Daniel Farina
Дата:
Сообщение: Re: CLOG extension