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

Re: SOC & user quotas

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, "Sergey E(dot) Koposov" <math(at)sai(dot)msu(dot)ru>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Subject: Re: SOC & user quotas
Date: 2007-03-02 18:58:21
Message-ID: 200703021358.21860.xzilla@users.sourceforge.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thursday 01 March 2007 17:35, Andrew Dunstan wrote:
> Tom Lane wrote:
> > "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> >> Andrew Dunstan wrote:
> >>> Hitting a file system quota limit is likely to bring you down pretty
> >>> hard, isn't it?
> >>
> >> Yes, and likely corrupt the database.
> >
> > As long as you don't keep WAL on the restricted filesystem, it won't
> > stop or corrupt your database.  Whether you can get anything much done
> > is another story :-(
>
> Yeah. Including recovery. Maybe we could do something that would work in
> cooperation with FS quotas - I have no idea what though.
>

I've actually run postgresql systems out of disk space both on data partitions 
and wal partitions and never suffered corruption.  Certainly I don't 
recommend the practice, but pg can be amazingly resilient at times. 

-- 
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

In response to

pgsql-hackers by date

Next:From: Bricklen AndersonDate: 2007-03-02 19:03:29
Subject: Re: UPSERT
Previous:From: Joshua D. DrakeDate: 2007-03-02 18:55:01
Subject: Re: Patch license update to developer's FAQ

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