Re: Adding ddl audit trigger
| От | Scott Marlowe |
|---|---|
| Тема | Re: Adding ddl audit trigger |
| Дата | |
| Msg-id | AANLkTik+WzY=GTWMuUc+YpYWg3ZN40CyDP4fQRQHJvDq@mail.gmail.com обсуждение исходный текст |
| Ответ на | Adding ddl audit trigger (Lawrence Cohan <LCohan@web.com>) |
| Ответы |
Re: Adding ddl audit trigger
|
| Список | pgsql-general |
On Wed, Jan 26, 2011 at 2:29 PM, Lawrence Cohan <LCohan@web.com> wrote: > 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: Yep, can't do it just yet. For now you've got log_statement='ddl'; which can be set by user, db, or for the whole cluster in postgresql.conf. You can use the log_line_prefix to see what user did what to which database. Then you can just grep for alter / create / drop etc. and see what's happened. not as slick or elegant as ddl triggers, but at least it's there.
В списке pgsql-general по дате отправления: