X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id F16FF53E0B for ; Mon, 9 May 2005 19:04:10 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 99931-04 for ; Mon, 9 May 2005 22:04:04 +0000 (GMT) Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.116.145.2]) by svr1.postgresql.org (Postfix) with ESMTP id 2406252A38 for ; Mon, 9 May 2005 19:04:03 -0300 (ADT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 68F3330953; Tue, 10 May 2005 00:01:53 +0200 (MET DST) From: Chris Browne X-Newsgroups: pgsql.performance Subject: Re: PGSQL Capacity Date: Mon, 09 May 2005 17:46:23 -0400 Organization: cbbrowne Computing Inc Lines: 29 Message-ID: <60ll6oul74.fsf@dba2.int.libertyrms.com> References: <1115666560.427fb8803c3a6@imp1-q.free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, linux) Cancel-Lock: sha1:BELzdprwblh0XYVrPHc+Kb0gKU8= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.155 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200505/124 X-Sequence-Number: 12288 bouchia.nazha@free.fr writes: > How can i know a capacity of a pg database ? > How many records my table can have ? > I saw in a message that someone have 50 000 records it's possible in a table ? > (My table have 8 string field (length 32 car)). > Thanks for your response. The capacity is much more likely to be limited by the size of the disk drives and filesystems you have available to you than by anything else. If your table consists of 8- 32 character strings, then each tuple will consume around 256 bytes of memory, and you will be able to fit on the order of 30 tuples into each 8K page. By default, you can extend a single table file to up to 1GB before it splits off to another piece. That would mean each file can have about 3.9M tuples. From there, you can have as many 1GB pieces as the disk will support. So you could have (plenty * 3.9M tuples), which could add up to be rather large. If you're expecting 50K records, that will be no big deal at all. -- (format nil "~S@~S" "cbbrowne" "acm.org") http://www.ntlug.org/~cbbrowne/sap.html Rules of the Evil Overlord #78. "I will not tell my Legions of Terror "And he must be taken alive!" The command will be: ``And try to take him alive if it is reasonably practical.''"