Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229])
	by mail.postgresql.org (Postfix) with ESMTP id 6DDAA17A3628
	for <pgsql-admin@postgresql.org>; Wed, 11 Jul 2012 15:27:15 -0300 (ADT)
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <tgl@sss.pgh.pa.us>) id 1Sp1d0-0002Rl-2q
	for pgsql-admin@postgresql.org; Wed, 11 Jul 2012 18:27:14 +0000
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q6BIQmJY015820;
	Wed, 11 Jul 2012 14:26:48 -0400 (EDT)
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Arnold, Sandra" <ArnoldS@osti.gov>
cc: "'Joshua D. Drake'" <jd@commandprompt.com>,
	"pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: What happens when PostgreSQL fails to log to SYSLOG
In-reply-to: <54E5385D47A89542BC678F5426799F3905261D4259@OSTIEX01.osti.gov>
References: <54E5385D47A89542BC678F5426799F3905261D424F@OSTIEX01.osti.gov>
	<4FFC911C.4010107@commandprompt.com>
	<54E5385D47A89542BC678F5426799F3905261D4259@OSTIEX01.osti.gov>
Comments: In-reply-to "Arnold, Sandra" <ArnoldS@osti.gov>
	message dated "Wed, 11 Jul 2012 13:47:56 -0400"
Date: Wed, 11 Jul 2012 14:26:48 -0400
Message-ID: <15819.1342031208@sss.pgh.pa.us>
X-Pg-Spam-Score: -1.9 (-)
X-Archive-Number: 201207/34
X-Sequence-Number: 39751

"Arnold, Sandra" <ArnoldS@osti.gov> writes:
> Tablelog would be ok for keeping up with transactions for tables.
> However, we also need to audit who connects successfully and
> unsuccessfully.  As far as I am aware, if a user fails to log in
> successfully, say three times, PostgreSQL is not able to lock the
> account for 9.0.

If you want custom authorization rules like that, the usual
recommendation is to use PAM authentication; you can set up pretty much
anything you want with a few PAM modules.

			regards, tom lane