From: Tom Lane <tgl@sss.pgh.pa.us>
To: Arnold, Sandra <ArnoldS@osti.gov>
Cc: 'Joshua D. Drake' <jd@commandprompt.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: What happens when PostgreSQL fails to log to SYSLOG
Date: Wed, 11 Jul 2012 14:26:48 -0400
Message-ID: <15819.1342031208@sss.pgh.pa.us> (raw)
In-Reply-To: <54E5385D47A89542BC678F5426799F3905261D4259@OSTIEX01.osti.gov>
References: <54E5385D47A89542BC678F5426799F3905261D424F@OSTIEX01.osti.gov>
<4FFC911C.4010107@commandprompt.com>
<54E5385D47A89542BC678F5426799F3905261D4259@OSTIEX01.osti.gov>
"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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, ArnoldS@osti.gov, jd@commandprompt.com
Subject: Re: What happens when PostgreSQL fails to log to SYSLOG
In-Reply-To: <15819.1342031208@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox