MIME-Version: 1.0
References: <CA+FnnTw1fUZz8=4gqKFgfXw2RePNxpy1JjcPtD2w3vh6mdXhQw@mail.gmail.com>
 <bf759988-5f40-4280-855e-2d0cbe2f41b0@aklaver.com>
In-Reply-To: <bf759988-5f40-4280-855e-2d0cbe2f41b0@aklaver.com>
From: Igor Korot <ikorot01@gmail.com>
Date: Fri, 7 Feb 2025 13:02:19 -0600
Message-ID: <CA+FnnTwe-JrnToK1tZD9J+ZMMM571cSvX3tyf0i3feL7QWSDOA@mail.gmail.com>
Subject: Re: How to get a notification
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CA%2BFnnTwe-JrnToK1tZD9J%2BZMMM571cSvX3tyf0i3feL7QWSDOA%40mail.gmail.com>
Precedence: bulk

Hi, Adrian,

On Fri, Feb 7, 2025 at 11:07=E2=80=AFAM Adrian Klaver <adrian.klaver@aklave=
r.com> wrote:
>
> On 2/5/25 23:21, Igor Korot wrote:
> > Hi, ALL,
> > In my code I'm running following:
> >
> >              queries.push_back( L"CREATE FUNCTION
> > __watch_schema_changes() RETURNS event_trigger LANGUAGE plpgsql AS $$
> > BEGIN NOTIFY tg_tag; END; $$;" );
> >              queries.push_back( L"CREATE EVENT TRIGGER
> > schema_change_notify ON ddl_command_end WHEN TAG IN(\'CREATE TABLE\',
> > \'ALTER TABLE\', \'DROP TABLE\', \'CREATE INDEX\', \'DROP INDEX\')
> > EXECUTE PROCEDURE __watch_schema_changes();" );
> >
> > My questions are:
> > 1 Is there a better way to get notification about CREATE/ALTER/DROP TAB=
LE?
>
> An alternate solution:
>
> https://www.pgaudit.org/
>
> Whether it is better or not is something you will need to decide.
>
> > 2. How do I receive notification abut the event with the object name?
>
> Use information from here?:
>
> https://www.postgresql.org/docs/current/functions-event-triggers.html#PG-=
EVENT-TRIGGER-DDL-COMMAND-END-FUNCTIONS

Thx for the link
So basically all I need to do is to call

SELECT pg_event_trigger_ddl_commands ()

right?

In both ODBC amd libpq interfaces?

Thank you.


>
> >
> > Thank you.
> >
> >
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
>