On Wed, Jul 11, 2012 at 10:47 AM, Arnold, Sandra wrote:
> 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, PostgreSQ
"Arnold, Sandra" 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
> accou
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. Is this the case fo
