| From: | "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com> |
|---|---|
| To: | pgsql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Pet Peeves? |
| Date: | 2009-02-04 16:25:50 |
| Message-ID: | 1D87A4B9-F7A2-4296-B873-734CA8CC046E@themactionfaction.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Feb 3, 2009, at 11:55 PM, 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?
What about LISTEN/NOTIFY events? That would be one way to create
autonomous transactions.
Cheers,
M
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris.Ellis | 2009-02-04 16:42:05 | Re: field with Password |
| Previous Message | Sam Mason | 2009-02-04 15:22:47 | Re: ramblings about password exposure (WAS: field with Password) |