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

table file size

From: Fred(dot)Zellinger(at)seagate(dot)com
To: pgsql-admin(at)postgresql(dot)org
Subject: table file size
Date: 2000-11-10 22:48:43
Message-ID: OFC4217BAF.E6FDDA4F-ON86256993.007D1E43@stsv.seagate.com (view raw or flat)
Thread:
Lists: pgsql-admin
I looked for this in the code and couldn't find it, but I agree.  Being
able to set the table file size to something like 650Mb(the size of a
burnable CD) would be useful for disaster recovery solutions.

---------------------- Forwarded by Fred Zellinger on 11/10/2000 04:46 PM
---------------------------


Charlie Crissman <CCrissman(at)nbibx(dot)com>@postgresql.org on 11/10/2000
09:08:10 AM

Sent by:  pgsql-admin-owner(at)postgresql(dot)org


To:   "'pgsql-admin(at)postgresql(dot)org'" <pgsql-admin(at)postgresql(dot)org>
cc:

Subject:  [ADMIN] table file size


I recently learned that the file for a table (class) will grow to 1G and
then a new file ('tablename.1') will be created and the table will grow
into
that one, etc...

Is this tunable in any way?  Can we change that 1G value for growth or for
the base file?

I am able to put links in place for 'tablename.1', 'tablename.2', etc.. and
they are used without error as the table grows into them, but I would like
to not have 1G taken up by the base file before it grows and uses the links
I create.

Thanks, Charlie Crissman

Charlie Crissman
Sr. Oracle DBA
Oracle Certified Professional DBA
No Boundaries Network, Inc.
904-245-6839
Pager 904-840-3684
mailto:CCrissman(at)nbibx(dot)com <mailto:CCrissman(at)nbibx(dot)com>
Before you criticize someone, you should walk a mile in their shoes.
That way, when you criticize them, you're a mile away and you have their
shoes.




pgsql-admin by date

Next:From: Gavin M. RoyDate: 2000-11-11 03:27:51
Subject: Upgrade
Previous:From: Jie LiangDate: 2000-11-10 17:58:38
Subject: Re: is a user in a group?

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