Re: CLOG extension - Mailing list pgsql-hackers

From Daniel Farina
Subject Re: CLOG extension
Date
Msg-id CAAZKuFaiKcpde134+rY1+_035Z_f-Lfnd-S8=kQvNNV7jKqwdA@mail.gmail.com
Whole thread Raw
In response to Re: CLOG extension  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: CLOG extension
List pgsql-hackers
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?

This may be related to some of the nascent work mentioned recently on
allowing for backend daemons, primarily for event scheduling.

Said Nap Commander could also possibly help with wakeups.

[0]: Credit to Will Leinweber for the memorable name.

--
fdr


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Advisory locks seem rather broken
Next
From: Tom Lane
Date:
Subject: Re: Advisory locks seem rather broken