| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pre-commit triggers |
| Date: | 2013-11-26 17:45:26 |
| Message-ID: | 9974.1385487926@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
It's far from committable, of course, but there is somebody working on it.
I tend to agree with the complaints that pre-commit triggers in the
proposed form would be pretty useless. You'd have to code in C to get
any useful information about what the transaction had done (and you'd
still not have much), but if you're coding in C there's already a hook
you can use for this.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2013-11-26 17:55:37 | Re: Cleaner build output when not much has changed |
| Previous Message | Fujii Masao | 2013-11-26 17:40:36 | Re: New option for pg_basebackup, to specify a different directory for pg_xlog |