Guy Rouillier wrote:
And someone else might want to play that game inside PG ;).
In fact, given how extensible PG is in other ways, it's surprising there hasn't been more call for it. Perhaps the fact there there's presently no facility for stored procedures to easily manage transactions has something to do with it?
An internal job scheduler with the ability to fire jobs on certain events as well as on a fixed schedule could be particularly handy in conjunction with true stored procedures that could explicitly manage transactions.
-- Craig Ringer -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
