| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Marco Nenciarini <marco(dot)nenciarini(at)2ndquadrant(dot)it>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] session_replication_role = replica with TRUNCATE |
| Date: | 2018-01-23 02:37:43 |
| Message-ID: | f230bcb5-e0a9-3f0c-7b13-2fb1ccc94cef@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/18/18 12:41, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>> So I'm proposing the attached alternative patch, which creates
>> constraint triggers to be TRIGGER_FIRES_ALWAYS by default.
>> Thoughts?
>
> Hm, the general idea seems attractive, but I'm not sure we want
> this behavioral change for user-created triggers. Can we make it
> happen like that only for RI triggers specifically? If not, there's
> at least some missing doco changes here.
I never quite understood the difference between a normal trigger and a
constraint trigger. But perhaps this should be it. If the purpose of a
constraint trigger is to enforce a constraint, then this should be the
default behavior, I think. You could always manually ALTER TABLE things.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2018-01-23 02:45:22 | Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation) |
| Previous Message | Peter Eisentraut | 2018-01-23 02:35:40 | Re: [PATCH] session_replication_role = replica with TRUNCATE |