Re: postgres event trigger workaround

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: "Zwettler Markus (OIZ)" <Markus(dot)Zwettler(at)zuerich(dot)ch>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: postgres event trigger workaround
Date: 2022-01-12 12:55:17
Message-ID: 20220112125517.idglbczyiargb56f@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

On Wed, Jan 12, 2022 at 11:57:45AM +0000, Zwettler Markus (OIZ) wrote:
>
> PG event triggers are not firing on CREATE ROLE, CREATE DATABASE, CREATE
> TABLESPACE by definition (would be nice if they do).
>
> Is there any workaround to react with ddl_command_start behavior on such an
> event?

That's not possible. The limitation exists because those objects are shared
objects and therefore could be created from any database in the cluster.

What is your use case? Maybe you could rely on logging all DDL instead for
instance.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Simon Riggs 2022-01-12 13:17:17 Re: pg_stat_statements
Previous Message Issa Gorissen 2022-01-12 12:22:22 WAL Archiving and base backup