Thanx for all the suggestions. I'm planning to go ahead with the trigger approach and locking databases for writes when it goes over the threshold! Setting hard limits looks like a bad idea !
cheers
/Dev
--- On Thu, 7/3/08, Tino Schwarze <postgresql@tisc.de> wrote:
From: Tino Schwarze <postgresql@tisc.de> Subject: Re: [ADMIN] Best way to limit database sizes To: pgsql-admin@postgresql.org Date: Thursday, July 3, 2008, 9:17 PM
On Thu, Jul 03, 2008 at 09:10:47PM +0200, Dimitri Fontaine wrote:
> >I've considered creating a tablespace in a directory owned by the
> >user , so I can use Linux quotas to prevent higher disk usage , but > >this turned out be abad thought, as all the files are anyway owned > >by the postgres user and so disk quotas won't have any effect. > > What if you put each tablespace on a LVM partition of a control sized, > extensible?
This is a desaster waiting to happen. I'd say never let a database get out of disk space. Rather implement soft limits like regular cron jobs and make them pay for overusage.
Also note that DB size on disk and amount of data stored in DB might be a lot different because of bloating issues, indices etc.
Tino..oO(But LVM/tablespace should work.)
-- "What we nourish flourishes." - "Was wir nähren erblüht."
www.craniosacralzentrum.de www.forteego.de
-- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin