Re: event triggers in 9.3.4 - Mailing list pgsql-general

From Vasudevan, Ramya
Subject Re: event triggers in 9.3.4
Date
Msg-id 20EE50F73664E744AF948F0106FE6DFA585A7DDD@SEAMBX01.sea.corp.int.untd.com
Whole thread Raw
In response to Re: event triggers in 9.3.4  (hubert depesz lubaczewski <depesz@gmail.com>)
Responses Re: event triggers in 9.3.4
Re: event triggers in 9.3.4
List pgsql-general

>> You could compare list of tables before (_start) and after (_end) the ddl. Doing it in plpgsql will be tricky, but if you'd use some other language - like plperl - it's relatively simple:  http://www.depesz.com/2013/12/18/waiting-for-9-4-plperl-add-event-trigger-support/

Thank You Depesz.  This will work for ‘CREATE’ and ‘DROP’ DDLs.

 

But, what about the scenario where I want to just have event triggers for operations like these? - 'ALTER TABLE','ALTER TRIGGER', 'ALTER FUNCTION'

CREATE EVENT TRIGGER log_ddl_info_start

ON

ddl_command_start

when

tag in

('ALTER TABLE','ALTER TRIGGER','CREATE FUNCTION','ALTER FUNCTION')

EXECUTE PROCEDURE

log_ddl_execution();

 

In this case, is there a way to capture the object that was altered?

 

Thank You

Ramya

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: tab_to_sting
Next
From: Seref Arikan
Date:
Subject: Are queries run completely before a Cursor can be used?