> To: Arnold, Sandra
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] What happens when PostgreSQL fails to log to SYSLOG
>
>
> On 07/10/2012 01:08 PM, Arnold, Sandra wrote:
> > I am trying to find out what PostgreSQL does when it cannot write to
> > its SYSLOG file, whet
"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
: Joshua D. Drake [mailto:j...@commandprompt.com]
Sent: Tuesday, July 10, 2012 4:31 PM
To: Arnold, Sandra
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] What happens when PostgreSQL fails to log to SYSLOG
On 07/10/2012 01:08 PM, Arnold, Sandra wrote:
> I am trying to find out what PostgreSQL d
On 07/10/2012 01:08 PM, Arnold, Sandra wrote:
I am trying to find out what PostgreSQL does when it cannot write to its
SYSLOG file, whether it is permissions or the file system where the log
resides is full is the problem.
PostgreSQL doesn't write to a SYSLOG file. It sends it to the syslog
d
I am trying to find out what PostgreSQL does when it cannot write to its SYSLOG
file, whether it is permissions or the file system where the log resides is
full is the problem. Does PostgreSQL stall, does it rollback the transaction
it cannot log to the SYSLOG, or does it continue on as if ther
