From: Tino Schwarze <postgresql@tisc.de>
To: pgsql-admin@postgresql.org
Subject: Re: Best way to limit database sizes
Date: Thu, 3 Jul 2008 21:17:36 +0200
Message-ID: <20080703191736.GB24555@easy2.in-chemnitz.de> (raw)
In-Reply-To: <08A677B0-4BE9-4F75-83F2-410DE6F360C3@hi-media.com>
References: <619537.42270.qm@web53708.mail.re2.yahoo.com>
<08A677B0-4BE9-4F75-83F2-410DE6F360C3@hi-media.com>
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 a bad 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: postgresql@tisc.de
Subject: Re: Best way to limit database sizes
In-Reply-To: <20080703191736.GB24555@easy2.in-chemnitz.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox