Can the log_statement parameter be set at the user level?

Started by Arnold, Sandraalmost 16 years ago3 messagesgeneral
Jump to latest
#1Arnold, Sandra
ArnoldS@osti.gov

Can the log_statement configuration parameter be set at the user level? For auditing purposes I need to capture certain statements being executed by specific accounts. However, there are some accounts that it would be nice not to be logging this information nor is it required. If log_statement can be set at the user level, then I can set it to not log 'mod' for the accounts that I do not want this detail.

Thanks,

Sandra Arnold
Sr. Database Administrator
NCI
DOE/OSTI
Oak Ridge, TN

#2Kevin Grittner
Kevin.Grittner@wicourts.gov
In reply to: Arnold, Sandra (#1)
Re: Can the log_statement parameter be set at the user level?

"Arnold, Sandra" <ArnoldS@osti.gov> wrote:

Can the log_statement configuration parameter be set at the user

level?

ALTER USER userid SET log_statement = 'none';

-Kevin

#3Scott Marlowe
scott.marlowe@gmail.com
In reply to: Arnold, Sandra (#1)
Re: Can the log_statement parameter be set at the user level?

On Tue, Apr 20, 2010 at 1:23 PM, Arnold, Sandra <ArnoldS@osti.gov> wrote:

Can the log_statement configuration parameter be set at the user level?  For
auditing purposes I need to capture certain statements being executed by
specific accounts.  However, there are some accounts that it would be nice
not to be logging this information nor is it required.  If log_statement can
be set at the user level, then I can set it to not log 'mod' for the
accounts that I do not want this detail.

Yep. As Kevin mentioned, it can be set by role / user. Also by
database and by cluster. User overrides db, db overrides cluster.