From: Thomas Swan <tswan@idigx.com>
To: josh@agliodbs.com
Cc: Eric <emayo@pozicom.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: Limiting database size
Date: Wed, 26 Jun 2002 18:41:49 -0500
Message-ID: <3D1A513D.30805@idigx.com> (raw)
References: <200206071442.36850.josh@agliodbs.com>
<afahdp$n9p$1@news.hub.org>
<200206261112.02982.josh@agliodbs.com>
Josh Berkus wrote:
>Eric,
>
>>I like the idea of putting it on a hard disk or partition of fixed size and
>>waiting for the DB to simply crash.
>>hahaha
>>
>>
>Yeah. <grin> It's what MS SQL Server does, though. As I said, I think the
>whole concept of limiting database size in MB is fundamentally flawed. I
>mean, what's the database supposed to do when it runs out of space?
>
Refuse updates, deletes, and inserts (from anything other than a DB
superuser). However you should be able to select data. Once the
database has exceeded its bounds, it would revert to read only status
and wait for administrative intervention such as enlarging the quota
(allocatable size) or altering the database to reduce its size.
Adding the checks wouldn't break existing databases if you defaulted the
checks to off.
This could also significantly help in hosting situations by preventing a
client for exceeding a specified quota and taking over the allocated
area for the postgres database.
Thinking about it, it seems like a good safety feature (aside from good
partitioning and system layout to begin with).
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-sql@postgresql.org
Cc: tswan@idigx.com, josh@agliodbs.com, emayo@pozicom.net
Subject: Re: Limiting database size
In-Reply-To: <3D1A513D.30805@idigx.com>
* 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