| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Lawrence Cohan <LCohan(at)web(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Adding ddl audit trigger |
| Date: | 2011-01-26 21:54:34 |
| Message-ID: | 4D40981A.1030407@lelarge.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le 26/01/2011 22:29, Lawrence Cohan a écrit :
> Trying to get some DDL auditing in a development environment by adding triggers to pg_proc, pg_class,pg_type,pg_trigger and getting the following error:
>
> ERROR: permission denied: "pg_proc" is a system catalog
> SQL state: 42501
>
> Is there any way to achieve DDL auditing in Postgres and trace any new/dropped/changed object into a table?
No. If there was, it would open new great possibilities for tools like
Slony or Londiste.
> All I need is to at least be able and save a userid(current_user), timestamp, action, and the name of the object and this could be done easily by adding triggers to these pg catalogs.
Nope, sorry. You can't add triggers on system catalogs.
--
Guillaume
http://www.postgresql.fr
http://dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-01-26 22:13:38 | Re: Adding ddl audit trigger |
| Previous Message | El Co | 2011-01-26 21:30:28 | Adding ddl audit trigger |