Re: CREATE TABLE LIKE INCLUDING TRIGGERS

From: lakshmi <lakshmigcdac(at)gmail(dot)com>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, 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-05-27 06:03:29
Message-ID: CAEvyyTizjWeieX4JEAnw8z2hrFYkUVDopJ2d+S6tdQW6tcdkbw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> 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
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2026-05-27 06:20:05 Re: Include schema-qualified names in publication error messages.
Previous Message vellaipandiyan sm 2026-05-27 05:54:06 Re: Can we use Statistics Import and Export feature to perforamance testing?