| From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pre-commit triggers |
| Date: | 2013-11-17 19:04:57 |
| Message-ID: | 52891359.40101@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/17/2013 07:31 PM, Andres Freund wrote:
> On 2013-11-17 09:39:26 +0100, Hannu Krosing wrote:
>>> Besides, exactly what would you do in such a trigger?
>> The use case would be telling another system about the rollback.
>>
>> Basically sending a "ignore what I told you to do" message
> But you can't rely on it - if e.g. the server restarted/crashed, there
> won't be any messages about it. In that light, I really don't see what
> you could do with it.
I can get the info about non-commit earlier :)
At some point I can call back into the database and see if the
transaction is still running.
Cheers
--
Hannu Krosing
PostgreSQL Consultant
Performance, Scalability and High Availability
2ndQuadrant Nordic OÜ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2013-11-17 20:02:59 | Re: additional json functionality |
| Previous Message | Martijn van Oosterhout | 2013-11-17 18:56:14 | Re: Wildcard usage enhancements in .pgpass |