| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Hannu Krosing <hannu(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 18:31:36 |
| Message-ID: | 20131117183136.GA19184@alap2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2013-11-17 18:56:14 | Re: Wildcard usage enhancements in .pgpass |
| Previous Message | Rohit Goyal | 2013-11-17 18:06:06 | Compile and test in netbeans |