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.
--
Guy Rouillier