Re: DETACH PARTITION and FOR EACH ROW triggers on partitioned tables

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: DETACH PARTITION and FOR EACH ROW triggers on partitioned tables
Дата
Msg-id 20200421154553.GA21155@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: DETACH PARTITION and FOR EACH ROW triggers on partitioned tables  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: DETACH PARTITION and FOR EACH ROW triggers on partitioned tables
Список pgsql-hackers
On 2020-Apr-20, Alvaro Herrera wrote:

> +    while (HeapTupleIsValid(trigtup = systable_getnext(scan)))
> +    {
> +        Form_pg_trigger pg_trigger = (Form_pg_trigger) GETSTRUCT(trigtup);
> +        ObjectAddress trig;
> +
> +        /* Ignore triggers that weren't cloned */
> +        if (!OidIsValid(pg_trigger->tgparentid) ||
> +            !pg_trigger->tgisinternal ||
> +            !TRIGGER_FOR_ROW(pg_trigger->tgtype))
> +            continue;

Actually, shouldn't we be checking just "!OidIsValid(pg_trigger->tgparentid)"
here?  Surely the other two conditions should already not matter either
way if tgparentid is set.  I can't see us starting to clone
for-statement triggers, but I'm not sure I trust the internal marking to
remain one way or the other.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: design for parallel backup
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: DETACH PARTITION and FOR EACH ROW triggers on partitioned tables