Thread: Limiting database size
Hi, is there any way to limit the database size??
[]'s Mauricio
Mauricio, > Hi, is there any way to limit the database size?? First, this is a question for PGSQL-NOVICE or PGSQL-GENERAL, not this mailing list. Second -- sort of. You can put the database on its own hard drive partition. Then the database will crash when it runs out of space -- so I'm not sure that helps you. Of course, with other RDBMSs, which have administrative settings for size limits, the database shuts down when you're out of space. So I'm not sure how useful the whole idea is. -- -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete informationtechnology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco
Hello, Mr. Bruce da Silva LEE, Put the Database directory into a pre-sized partition. Regards, -- Tulio Oliveira Internet DBA Telecontrol Networking --------- Mensagem Original -------- De: Maurício Sessue Otta <mauricio@cristorei.com.br> Para: pgsql-sql@postgresql.org <pgsql-sql@postgresql.org> Assunto: [SQL] Limiting database size Data: 07/06/02 17:36 > Hi, is there any way to limit the database size?? > > []'s Mauricio > > >
On Fri, 07 Jun 2002 16:37:03 -0400, Maurício Sessue Otta wrote: > Hi, is there any way to limit the database size?? You can limit a table's size (row count) by means of a rule or trigger. I don't think there's any good way to control the overall size (in bytes) of a database. -- Jeff Boes vox 616.226.9550 ext 24 Database Engineer fax 616.349.9076 Nexcerpt, Inc. http://www.nexcerpt.com ...Nexcerpt... Extend your Expertise
Hi Mauricio Novell, and i think windows and unix as well, have the disk quota feature. The disk size assigned to a user can be limited. There should also be warning levels in order to get the sysadmin noticed about a user running out of space before it's too late. Try on a os related newsgroup, they should know better! ulli "Maur�cio Sessue Otta" <mauricio@cristorei.com.br> schrieb im Newsbeitrag news:005a01c20e57$3dbdfcc0$8359e6c8@cristorei.com.br... > This is a multi-part message in MIME format. > > ------=_NextPart_000_0057_01C20E3E.0C7EE840 > Content-Type: text/plain; charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > Hi, is there any way to limit the database size?? > > []'s Mauricio
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 "Josh Berkus" <josh@agliodbs.com> wrote in message news:200206071442.36850.josh@agliodbs.com... > Mauricio, > > > Hi, is there any way to limit the database size?? > > First, this is a question for PGSQL-NOVICE or PGSQL-GENERAL, not this mailing > list. > > Second -- sort of. You can put the database on its own hard drive partition. > Then the database will crash when it runs out of space -- so I'm not sure > that helps you. > > Of course, with other RDBMSs, which have administrative settings for size > limits, the database shuts down when you're out of space. So I'm not sure > how useful the whole idea is. > > -- > -Josh Berkus > > ______AGLIO DATABASE SOLUTIONS___________________________ > Josh Berkus > Complete information technology josh@agliodbs.com > and data management solutions (415) 565-7293 > for law firms, small businesses fax 621-2533 > and non-profit organizations. San Francisco > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly >
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? -Josh
>> 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? Display a window that says: "Management has determined that this database shall not exceed XXXmb. If your business function requires more disk space - take it up with your manager." Limiting database size is not a problem for developers, unless they are unable/unwilling to explain to their management that disks are a whole lot less expensive than terminating a database application that depends them. But then, M$ never takes any responsibility for the amount of disk space it wastes..... terry
Josh Berkus wrote:<br /><blockquote cite="mid200206261112.02982.josh@agliodbs.com" type="cite"><pre wrap="">Eric,</pre><blockquotetype="cite"><pre wrap="">I like the idea of putting it on a hard disk or partition of fixedsize and waiting for the DB to simply crash. hahaha </pre></blockquote><pre wrap="">Yeah. <grin> It's what MS SQL Server does, though. As I said, I thinkthe 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?</pre></blockquote> Refuse updates, deletes, and inserts(from anything other than a DB superuser). However you should be able to select data. Once the database has exceededits 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.<br /><br /> Adding the checks wouldn't break existingdatabases if you defaulted the checks to off.<br /><br /> This could also significantly help in hosting situationsby preventing a client for exceeding a specified quota and taking over the allocated area for the postgres database.<br/><br /> Thinking about it, it seems like a good safety feature (aside from good partitioning and system layoutto begin with).<br /><br /><br /><br /><br />