Re: Audit Log Destination

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-admin(at)postgresql(dot)org
Cc: "Arnold, Sandra" <ArnoldS(at)osti(dot)gov>
Subject: Re: Audit Log Destination
Date: 2009-05-20 22:49:18
Message-ID: 200905210149.19038.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Moshe Ben-Shoham 2009-05-21 06:36:38 Inserts hang in DB and error messages in log
Previous Message Arnold, Sandra 2009-05-20 20:51:53 Audit Log Destination