Skip site navigation (1) Skip section navigation (2)

Re: Audit Log Destination

From: "Arnold, Sandra" <ArnoldS(at)osti(dot)gov>
To: "Peter Eisentraut" <peter_e(at)gmx(dot)net>,<pgsql-admin(at)postgresql(dot)org>
Subject: Re: Audit Log Destination
Date: 2009-05-21 14:29:05
Message-ID: FE7C49B620149C4EA12A474643D9EABF456391@OSTIEXCH.osti.gov (view raw or flat)
Thread:
Lists: pgsql-admin
Actually PostgreSQL calls it logging.  I am using the "csv" form of
logging.  I am logging connections, disconnections, and statements.  I
can use this for auditing purposes. 

-----Original Message-----
From: Peter Eisentraut [mailto:peter_e(at)gmx(dot)net] 
Sent: Wednesday, May 20, 2009 6:49 PM
To: pgsql-admin(at)postgresql(dot)org
Cc: Arnold, Sandra
Subject: Re: [ADMIN] Audit Log Destination

On Wednesday 20 May 2009 23:51:53 Arnold, Sandra wrote:
> One of my security controls is to audit events.  I don't have a
problem
> on how to do that.  However, another control is for all functionality
of
> the PostgreSQL database to cease or stall if the directory that
contains
> the audit logs is full.  What happens to PostgreSQL if any of the log
> directories are full and unable to have anything else written to it?
I
> have looked and cannot find anything that will tell me what happens.

PostgreSQL doesn't have the concept of an "audit log". So perhaps you
can 
explain exactly which functionality you are using for that purpose; then
we 
might figure out what happens when the disk is full.

In principle, however, you can try this out yourself, by creating a
limited-
size partition and pointing your log there.  That might give you a
better 
feeling for what exactly will happen.

In response to

pgsql-admin by date

Next:From: Tom LaneDate: 2009-05-21 14:30:35
Subject: Re: [GENERAL] compilation test fails
Previous:From: Ray StellDate: 2009-05-21 13:48:14
Subject: virtual savings

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group