Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> There is currently no way to run a separate daemon process that runs
> user code as part of Postgres, so that the startup code gets run
> immediately we startup, re-run if we crash and shut down cleanly when
> the server does. If there were some way to run arbitrary code in a
> daemon using an extensibility API then we wouldn't ever get any requests
> for the scheduler, cos you could write it yourself without troubling
> anybody here.
Please do include the Skytools / PGQ ticker as one use case in the
design discussion, and pgbouncer too. Having user daemons as part as the
PostgreSQL extensibility would be awesome indeed!
Bonus point if you build them with PGXS and install them from SQL, so
that the current extension packaging design applies.
I guess we can say that the archive and restore command are precursors
of managed user "daemons", or say, integrated processes. So adding them
to the use cases to cover would make sense.
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2010-02-21 22:11:16|
|Subject: Re: PGXS: REGRESS_OPTS=--load-language=plpgsql |
|Previous:||From: Bruce Momjian||Date: 2010-02-21 19:25:28|
|Subject: Re: PGXS: REGRESS_OPTS=--load-language=plpgsql|