| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pre-commit triggers |
| Date: | 2013-11-26 18:17:23 |
| Message-ID: | 5294E5B3.8060703@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/26/2013 09:45 AM, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> On 11/24/2013 06:42 AM, Simon Riggs wrote:
>>> I think we should be thinking harder about how to implement
>>> ASSERTIONs, possibly calling them ASSERTION TRIGGERs not pre-commit
>>> write event triggers.
>
>> I don't know that anyone is working on this, though, or even plans to.
>
> Huh?
> http://www.postgresql.org/message-id/1384486216.5008.17.camel@vanquo.pezone.net
Damn, I missed that. I'll have to check that out.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2013-11-26 18:36:12 | Re: Cleaner build output when not much has changed |
| Previous Message | Tom Lane | 2013-11-26 18:04:30 | Re: pre-commit triggers |