MIME-Version: 1.0
References: <CACJufxHJAr2FjbeB6ghg_-N5dxX5JVnjKSLOUxOyt4TeaAWQkg@mail.gmail.com>
 <CACJufxHQ8tDG09mXW=8xfEK2_h+By1zLgrFd0EcshHp-TDGiGw@mail.gmail.com>
 <CACJufxFu7Y4FhVkaKT2Kaj8ym2T5TcwN93cR_6h4x66iLrSZ-Q@mail.gmail.com>
 <CACJufxHMYq2ZqvOhoSKUmx+wZUo=HixjfgGKDJ6L4cdCvwh2VA@mail.gmail.com>
 <AF1AE30F-4379-462D-B321-FB1658230B5D@yandex-team.ru> <CACJufxH5YDMAQ_KXaPJaC4Zt1i2HNSNaYoskzNDRjSrE_UWjKw@mail.gmail.com>
 <CAN4CZFM_8jL7Rf43zLa-9P2BwC+_H-oM9kYxVLGcwu83KC6faA@mail.gmail.com>
In-Reply-To: <CAN4CZFM_8jL7Rf43zLa-9P2BwC+_H-oM9kYxVLGcwu83KC6faA@mail.gmail.com>
From: jian he <jian.universality@gmail.com>
Date: Thu, 22 Jan 2026 14:08:27 +0800
Message-ID: <CACJufxGGXnRP+Em521KvPVOmnPtya2zpPqrTuYDmrSY=AFVmfw@mail.gmail.com>
Subject: Re: CREATE TABLE LIKE INCLUDING TRIGGERS
To: Zsolt Parragi <zsolt.parragi@percona.com>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>, 
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CACJufxGGXnRP%2BEm521KvPVOmnPtya2zpPqrTuYDmrSY%3DAFVmfw%40mail.gmail.com>
Precedence: bulk

On Wed, Jan 21, 2026 at 8:13=E2=80=AFPM Zsolt Parragi <zsolt.parragi@percon=
a.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. Re=
fer
          to <link linkend=3D"sql-altertable"><command>ALTER
TABLE</command></link>
          to modify the firing condition.
         </para>

what do you think?


--
jian
https://www.enterprisedb.com/