Re: Collect ALTER PUBLICATION commands for event triggers

On Fri, Jul 24, 2026 at 9:03 PM Zhijie Hou (Fujitsu)
<houzj(dot)fnst(at)fujitsu(dot)com> wrote:
> I suspect this wasn't caught earlier because handling the dropped publication
> relation was sufficient to deparse it into the original ALTER PUBLICATION
> command (by combining multiple dropped items). I also assumed the primary use
> case for the event trigger was deparsing. I'm not opposed to also catching this
> command in ddl_end - I'm just curious whether it would address any additional
> use cases beyond what's already covered.

sql_drop may be sufficient for deparsing those cases. My concern is that
ddl_command_end fires, but pg_event_trigger_ddl_commands() reports
no corresponding ALTER PUBLICATION entry, which seems inconsistent
from a command-level auditing/logging perspective. So at least for me,
collecting the publication itself seems the right approach...

Regards,

--
Fujii Masao