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

From: Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>
Subject: Re: enable/disable broken for statement triggers on partitioned tables
Date: 2022-07-14 11:20:16
Message-ID: 388009b0-7fc7-4f6e-0c69-44df38413551@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I agree that the patch shouldn't have changed that behavior, so I've
> fixed the patch so that EnableDisableTrigger() recurses even if the
> parent trigger is unchanged.

Thanks, I think this patch is ready for committer.

--
With best regards,
Dmitry Koval

Postgres Professional: http://postgrespro.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sergey Dudoladov 2022-07-14 11:20:58 Re: Introduce "log_connection_stages" setting.
Previous Message Nikolay Shaplov 2022-07-14 11:07:56 Re: Bug: Reading from single byte character column type may cause out of bounds memory reads.