Re: Event Triggers unable to capture the DDL script executed - Mailing list pgsql-general

From Laurenz Albe
Subject Re: Event Triggers unable to capture the DDL script executed
Date
Msg-id 714b89f449005ed4348e2114f6ce5f8aff18ea8a.camel@cybertec.at
Whole thread Raw
In response to Event Triggers unable to capture the DDL script executed  (Neethu P <neeth_3@hotmail.com>)
Responses RE: Event Triggers unable to capture the DDL script executed  (<n.kobzarev@aeronavigator.ru>)
List pgsql-general
On Wed, 2023-02-22 at 07:57 +0000, Neethu P wrote:
> We are using event triggers to capture the DDL changes in a postgres database.
> However, we are unable to get the column information & the actual DDL script
> executed, while a table is altered. 
> Also, in the postgres documentation for pg_event_trigger_ddl_commands ()- it is mentioned as below.
> pg_ddl_command    A complete representation of the command, in internal
> format. Thiscannot be output directly, but it can be passed to other functions
> to obtain different pieces of information about the command.
>
> Is it possible to access pg_ddl_command in postgresql? Or is there any scripts
> which can help to get theactual Alter DDL statement that was executed by the user? 

That is simple if you write the event trigger in C.  I would say that that is the
only way to get at the actual statement.

Yours,
Laurenz Albe



pgsql-general by date:

Previous
From: HECTOR INGERTO
Date:
Subject: PostgreSQL optimizations for CoW FS
Next
From:
Date:
Subject: RE: Event Triggers unable to capture the DDL script executed