| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | Guy Rouillier <guyr-ml1(at)burntmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Pet Peeves? |
| Date: | 2009-02-04 05:11:45 |
| Message-ID: | dcc563d10902032111m13093f52i743bf020e1cc5cac@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Feb 3, 2009 at 10:09 PM, Craig Ringer
<craig(at)postnewspapers(dot)com(dot)au> wrote:
> Guy Rouillier wrote:
>>
>> Craig Ringer wrote:
>>>
>>> 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, 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.
other than schedule it to go off at certain times, not much you can't do.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Schwaighofer Clemens | 2009-02-04 05:51:45 | Re: problem converting database to UTF-8 |
| Previous Message | Craig Ringer | 2009-02-04 05:09:22 | Re: Pet Peeves? |