| From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
|---|---|
| To: | Nico Williams <nico(at)cryptonector(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COMMIT TRIGGERs, take n, implemented with CONSTRAINT TRIGGERS |
| Date: | 2017-09-15 08:10:38 |
| Message-ID: | CAPpHfduc9kcNCkA95Bc+NzzeX4i=b3k8GwHvx9+EPMnP9P9kwg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 14, 2017 at 10:41 PM, Nico Williams <nico(at)cryptonector(dot)com>
wrote:
> https://github.com/twosigma/postgresql-contrib/
> https://github.com/twosigma/postgresql-contrib/blob/
> master/commit_trigger.sql
> https://raw.githubusercontent.com/twosigma/postgresql-
> contrib/master/commit_trigger.sql
Do I understand correctly that this is SQL implementation of COMMIT TRIGGER
functionality which is a prototype used to demonstrate it. And if this
prototype is well-accepted then you're going to write a patch for builtin
COMMIT TRIGGER functionality. Is it right?
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Knizhnik | 2017-09-15 08:16:05 | Re: Surjective functional indexes |
| Previous Message | Tsunakawa, Takayuki | 2017-09-15 07:54:28 | Re: Re: [bug fix] PG10: libpq doesn't connect to alternative hosts when some errors occur |