| From: | jian he <jian(dot)universality(at)gmail(dot)com> |
|---|---|
| To: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CREATE TABLE LIKE INCLUDING TRIGGERS |
| Date: | 2026-01-22 06:08:27 |
| Message-ID: | CACJufxGGXnRP+Em521KvPVOmnPtya2zpPqrTuYDmrSY=AFVmfw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 21, 2026 at 8:13 PM Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote:
>
> Hello!
>
> I tested the patch, it works as described, but I did notice one possible issue:
>
> Shouldn't this preserve the enabled state of the triggers, or if it
> doesn't, should the documentation include this limitations?
>
I intended to document it as
<para>
All non-internal triggers on the original table will be
created on the new table.
By default, these triggers fire in "origin" and "local" modes. Refer
to <link linkend="sql-altertable"><command>ALTER
TABLE</command></link>
to modify the firing condition.
</para>
what do you think?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2026-01-22 06:09:37 | Re: Likely undefined behavior with some flexible arrays |
| Previous Message | Chao Li | 2026-01-22 05:57:27 | Re: Avoid recalculating pgprocno in ProcArrayAdd() |