Attention:
The information contained in this message and or attachments is intended only
for the person or entity to which it is addressed and may contain confidential
and/or privileged material. Any review, retransmission, dissemination or other
use of, or tak
Attention:
The information contained in this message and or attachments is intended only
for the person or entity to which it is addressed and may contain confidential
and/or privileged material. Any review, retransmission, dissemination or other
use of, or tak
Attention:
The information contained in this message and or attachments is intended only
for the person or entity to which it is addressed and may contain confidential
and/or privileged material. Any review, retransmission, dissemination or other
use of, or tak
Attention:
The information contained in this message and or attachments is intended only
for the person or entity to which it is addressed and may contain confidential
and/or privileged material. Any review, retransmission, dissemination or other
use of, or tak
We'll do that - thanks again.
-Original Message-
From: Scott Marlowe [mailto:scott.marl...@gmail.com]
Sent: January-27-11 3:58 PM
To: Lawrence Cohan
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Adding ddl audit trigger
On Thu, Jan 27, 2011 at 1:47 PM, Lawrence Cohan
That should do it for our dev environment however on production systems it
would be a little bit harder (quite a few hops/approval/restore) to get to and
grep the log files.
Many thanks for the suggestion,
Lawrence Cohan.
-Original Message-
From: Scott Marlowe [mailto:scott.marl
DDL
triggers that would be added DISABLED by default and users can turn them on/off
at their will.
Regards,
Lawrence Cohan.
-Original Message-
From: Guillaume Lelarge [mailto:guilla...@lelarge.info]
Sent: January-26-11 5:41 PM
To: Tom Lane
Cc: Lawrence Cohan; pgsql-general
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
ne
