Hi, We've been talking about this topic on -performance:
Markus Wanner <mar...@bluegap.ch> writes: > I've combined these two components into a single, general purpose background > worker infrastructure component, which is now capable to serve autovacuum as > well as Postgres-R. And it might be of use for other purposes as well, most > prominently parallel query processing. Basically anything that needs a > backend connected to a database to do any kind of background processing, > possibly parallelized. Magnus Hagander <mag...@hagander.net> writes: > On Tue, Jul 13, 2010 at 16:42, Dimitri Fontaine <dfonta...@hi-media.com> > wrote: >> So a supervisor daemon with a supervisor API that would have to support >> autovacuum as a use case, then things like pgagent, PGQ and pgbouncer, >> would be very welcome. >> >> What about starting a new thread about that? Or you already know you >> won't want to push the extensibility of PostgreSQL there? > > +1 on this idea in general, if we can think up a good API - this seems > very useful to me, and you have some good examples there of cases > where it'd definitely be a help. So, do you think we could use your work as a base for allowing custom daemon code? I guess we need to think about how to separate external code and internal code, so a second layer could be necessary here. As far as the API goes, I have several ideas but nothing that I have already implemented, so I'd prefer to follow Markus there :) Regards, -- dim -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
