| From: | Nico Williams <nico(at)cryptonector(dot)com> |
|---|---|
| To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COMMIT TRIGGERs, take n, implemented with CONSTRAINT TRIGGERS |
| Date: | 2017-09-15 13:12:07 |
| Message-ID: | CAK3OfOgPKDZB7XtCJODqJGkJm2JR9=N5weRZvZhLkeMse5BGKA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 15, 2017 at 4:11 AM Alexander Korotkov <
a(dot)korotkov(at)postgrespro(dot)ru> wrote:
> 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?
>
That's the idea, yes.
Nico
--
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2017-09-15 13:34:34 | Re: The case for removing replacement selection sort |
| Previous Message | Alexander Korotkov | 2017-09-15 12:53:09 | Re: Allow GiST opcalsses without compress\decompres functions |