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>
 <CACJufxGGXnRP+Em521KvPVOmnPtya2zpPqrTuYDmrSY=AFVmfw@mail.gmail.com>
 <CAN4CZFNPE_UeTEy5TH9wwc6mBAtX7vnBhLSL47jRiHXA=6yXjQ@mail.gmail.com>
 <CACJufxGTxbpbaQjUxc69-Dovx6+KJd=81T5111uizUrdsEkDNQ@mail.gmail.com>
 <CAN4CZFOdet_ZZEr+sZhTUiAd-fjOprhMXDhkjdhz48pEoJc9Pg@mail.gmail.com>
 <CACJufxEKK44FtxiShTZtPtCehwm47k5wB+RobuRCUJRa_b0owg@mail.gmail.com>
 <CACJufxFT-P-QZ-w5tVKOicWayUb1p407mWTDX5CGbf6XP2MGcA@mail.gmail.com>
 <CACJufxGhZy9s1ZZhOOu95AMpynk5acVxFVqHqoYcbbscezrbMA@mail.gmail.com>
In-Reply-To: 
 <CACJufxGhZy9s1ZZhOOu95AMpynk5acVxFVqHqoYcbbscezrbMA@mail.gmail.com>
From: lakshmi <lakshmigcdac@gmail.com>
Date: Wed, 27 May 2026 11:33:29 +0530
Message-ID: 
 <CAEvyyTizjWeieX4JEAnw8z2hrFYkUVDopJ2d+S6tdQW6tcdkbw@mail.gmail.com>
Subject: Re: CREATE TABLE LIKE INCLUDING TRIGGERS
To: jian he <jian.universality@gmail.com>
Cc: Zsolt Parragi <zsolt.parragi@percona.com>,
 Andrey Borodin <x4mmm@yandex-team.ru>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000b0de8c0652c6600c"
Archived-At: 
 <https://www.postgresql.org/message-id/CAEvyyTizjWeieX4JEAnw8z2hrFYkUVDopJ2d%2BS6tdQW6tcdkbw%40mail.gmail.com>
Precedence: bulk

--000000000000b0de8c0652c6600c
Content-Type: text/plain; charset="UTF-8"

>
> Hi Jian,
>
> I applied the latest v9 patches on current master and tested them locally.
>
> The patches applied cleanly, PostgreSQL built successfully.
>
> I also did some manual testing for INCLUDING TRIGGERS. Trigger definitions
> were copied correctly to the new table, and the trigger enabled/disabled
> state (tgenabled) was also preserved properly after applying the second
> patch.
>
> Everything worked as expected in my testing.
>
> Thanks for working on this feature.
>
> Regards,
> Lakshmi G
>

--000000000000b0de8c0652c6600c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote gmail_quote_container"><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><p class=3D"gmail-isSelectedEnd">H=
i Jian,</p><p class=3D"gmail-isSelectedEnd">I applied the latest v9 patches=
 on current master and tested them locally.</p><p class=3D"gmail-isSelected=
End">The patches applied cleanly, PostgreSQL built successfully.</p><p clas=
s=3D"gmail-isSelectedEnd">I also did some manual testing for INCLUDING TRIG=
GERS. Trigger definitions were copied correctly to the new table, and the t=
rigger enabled/disabled state (tgenabled) was also preserved properly after=
 applying the second patch.</p><p class=3D"gmail-isSelectedEnd">Everything =
worked as expected in my testing.</p><p class=3D"gmail-isSelectedEnd">Thank=
s for working on this feature.</p><p>Regards,<br>Lakshmi G</p>
</blockquote></div></div>

--000000000000b0de8c0652c6600c--