On Wed, Feb 04, 2009 at 12:37:31PM -0500, Guy Rouillier wrote: > Karsten Hilbert wrote: >>>> Craig, what kind of "events" are you thinking about? Triggers are >>>> already pieces of code that run upon "certain events", namely >>>> insert, update or delete events. What others do you have in mind? >>> That's a good point, actually. I can't think of much you can't do >>> with a trigger (SECURITY DEFINER if necessary) on a table. Not >>> thinking straight. >> >> I would find ON CONNECT/DISCONNECT triggers very useful. Probably >> this is more similar to database-wide assertions. > > But a job scheduler would not help with that. Perhaps you intended your > comment to fall into the "pet peeves" bucket rather than the "job > scheduler" bucket. Yep, just like the Subject suggested ;-) The logic is a bit twisted but I was thinking "other kinds of events - oh, I'd like to be able to make something happen on this event". Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
