Received: from maia.hub.org (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id A0B90633A9F;
	Tue, 20 Apr 2010 18:37:25 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia,
	port 10024)
	with ESMTP id 51437-05-2; Tue, 20 Apr 2010 21:37:15 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-gx0-f214.google.com (mail-gx0-f214.google.com
	[209.85.217.214])
	by mail.postgresql.org (Postfix) with ESMTP id 9F2E3633ECD;
	Tue, 20 Apr 2010 18:37:05 -0300 (ADT)
Received: by gxk6 with SMTP id 6so294585gxk.14
	for <multiple recipients>; Tue, 20 Apr 2010 14:37:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:date:received:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	bh=1shI6sBckeLmehSfbw3UGbPs4EgdUdUcInsE3aouHak=;
	b=lTrI1WX0YmSIYYin4oTX4ugjIQ1azYjtALTOLxlGuD/ujT8fLgvOmxegHji+V5XjQ/
	1vhvLNJl6NehZbc4CnAQAl54T2NTtrpvMkAHHFqSFxQFyIHYmTxIZHSiz91g20y+gfiw
	YN5OUIzWYKOjJVEOcVurRT1QM4kcvVA51abHM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=rXiYwIXQRM/r7+bw4gxM+u60ZgzseEHhJK/rwEerrS9mLBM5jonM2RyXKsjrTzYMcH
	Zp0hsOyNsuxa3xLNvI0pT7EpV/hcvthte5GQild99yCWPP7HQwXSZkLTGqvDUplfn8uT
	0mOwDthRTI0ALaTO3tkjw31Q0/0goJkU5b730=
MIME-Version: 1.0
Received: by 10.150.218.9 with HTTP; Tue, 20 Apr 2010 14:37:04 -0700 (PDT)
In-Reply-To: <54E5385D47A89542BC678F5426799F390498CB3139@OSTIEX01.osti.gov>
References: <54E5385D47A89542BC678F5426799F390498CB3139@OSTIEX01.osti.gov>
Date: Tue, 20 Apr 2010 15:37:04 -0600
Received: by 10.150.117.34 with SMTP id p34mr7588438ybc.110.1271799424343;
	Tue, 20 Apr 2010 14:37:04 -0700 (PDT)
Message-ID: <t2sdcc563d11004201437s56e95a70r25ce2733759b25fd@mail.gmail.com>
Subject: Re: Can the log_statement parameter be set at the user level?
From: Scott Marlowe <scott.marlowe@gmail.com>
To: "Arnold, Sandra" <ArnoldS@osti.gov>
Cc: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>,
	"pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.899 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001
X-Spam-Level: 
X-Archive-Number: 201004/294
X-Sequence-Number: 34388

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?=
=A0 For
> auditing purposes I need to capture certain statements being executed by
> specific accounts.=A0 However, there are some accounts that it would be n=
ice
> not to be logging this information nor is it required.=A0 If log_statemen=
t 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.