Re: enable/disable broken for statement triggers on partitioned tables

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: enable/disable broken for statement triggers on partitioned tables
Дата
Msg-id 20220729184452.2i4xcru3lzey76m6@alvherre.pgsql
обсуждение исходный текст
Ответ на enable/disable broken for statement triggers on partitioned tables  (Amit Langote <amitlangote09@gmail.com>)
Ответы Re: enable/disable broken for statement triggers on partitioned tables  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On 2022-May-24, Amit Langote wrote:

> So, I think we should do something like the attached.  A lot of
> boilerplate is needed given that the various enable/disable trigger
> variants are represented as separate sub-commands (AlterTableCmd
> subtypes), which can perhaps be avoided by inventing a
> EnableDisableTrigStmt sub-command node that stores (only?) the recurse
> flag.

Yeah, I don't know about adding tons of values to that enum just so that
we can use that to hide a boolean inside.  Why not add a boolean to the
containing struct?  Something like the attached.

We can later use the same thing to undo what happens in in AddColumn,
DropColumn, etc.  It all looks pretty strange and confusing to me.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"Investigación es lo que hago cuando no sé lo que estoy haciendo"
(Wernher von Braun)

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: making relfilenodes 56 bits
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: Documentation about PL transforms