| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Arnold, Sandra" <ArnoldS(at)osti(dot)gov> |
| Cc: | "'Joshua D(dot) Drake'" <jd(at)commandprompt(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: What happens when PostgreSQL fails to log to SYSLOG |
| Date: | 2012-07-11 18:26:48 |
| Message-ID: | 15819.1342031208@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Arnold, Sandra" <ArnoldS(at)osti(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig James | 2012-07-11 20:07:59 | Re: What happens when PostgreSQL fails to log to SYSLOG |
| Previous Message | Arnold, Sandra | 2012-07-11 17:47:56 | Re: What happens when PostgreSQL fails to log to SYSLOG |