X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id F32153A3DD7 for ; Tue, 4 Jan 2005 08:51:07 +0000 (GMT) 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 19263-08 for ; Tue, 4 Jan 2005 08:50:43 +0000 (GMT) Received: from curie.credativ.org (credativ.com [217.160.209.18]) by svr1.postgresql.org (Postfix) with ESMTP id 8602F3A3DE1 for ; Tue, 4 Jan 2005 08:50:43 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by curie.credativ.org (Postfix) with ESMTP id EDAC455EB7; Tue, 4 Jan 2005 09:50:39 +0100 (CET) Received: from www.credativ.de (pD9500AD4.dip0.t-ipconnect.de [217.80.10.212]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by curie.credativ.org (Postfix) with ESMTP id 543FE55EB6; Tue, 4 Jan 2005 09:50:39 +0100 (CET) Received: from bell.credativ.de (bell.credativ.de [172.26.14.16]) by www.credativ.de (Postfix) with ESMTP id 9A2F51C0014; Tue, 4 Jan 2005 09:50:36 +0100 (CET) From: Peter Eisentraut To: "Chris Hoover" Subject: Re: How to calculate row sizes Date: Tue, 4 Jan 2005 09:50:33 +0100 User-Agent: KMail/1.6.2 Cc: References: <200501032155.20181.peter_e@gmx.net> <41D9FB09.3060107@sermonaudio.com> In-Reply-To: <41D9FB09.3060107@sermonaudio.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501040950.34265.peter_e@gmx.net> X-Virus-Scanned: by AMaViS at credativ.com X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/19 X-Sequence-Number: 15878 Am Dienstag, 4. Januar 2005 03:10 schrieb Chris Hoover: > This faq is not very helpful. I really need to know the values for each > type of column, and then how much to add for the overhead. It only > gives a single example, and does not address the index size. Nor does > it give the storage size for the various column types. The storage requirements for each column type are quite evidently displayed in the documentation about the data types. The overhead is shown in the FAQ. If you want more precise values, create a table, fill it with values, run VACUUM FULL, and look at the file system size. That's the only way you can be sure. -- Peter Eisentraut http://developer.postgresql.org/~petere/