Re: enable/disable broken for statement triggers on partitioned tables - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: enable/disable broken for statement triggers on partitioned tables
Date
Msg-id 73027d59-bff7-d245-af90-c654a78a50c0@enterprisedb.com
Whole thread Raw
In response to Re: enable/disable broken for statement triggers on partitioned tables  (Zhihong Yu <zyu@yugabyte.com>)
Responses Re: enable/disable broken for statement triggers on partitioned tables  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
On 24.05.22 23:23, Zhihong Yu wrote:
> Hi,
> 
>      AT_EnableTrig,              /* ENABLE TRIGGER name */
> +   AT_EnableTrigRecurse,       /* internal to commands/tablecmds.c */
>      AT_EnableAlwaysTrig,        /* ENABLE ALWAYS TRIGGER name */
> +   AT_EnableAlwaysTrigRecurse, /* internal to commands/tablecmds.c */
> 
> Is it better to put the new enum's at the end of the AlterTableType?
> 
> This way the numeric values for existing ones don't change.

That's a concern if backpatching.  Otherwise, it's better to put them 
like shown in the patch.



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: generic plans and "initial" pruning
Next
From: Yugo NAGATA
Date:
Subject: Remove useless tests about TRUNCATE on foreign table