X-Original-To: pgsql-admin@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id EBEAB474E44 for ; Wed, 2 Apr 2003 16:12:03 -0500 (EST) Received: from mta04.onolab.com (smtp.ono.com [62.42.230.12]) by postgresql.org (Postfix) with ESMTP id 8FE27474E44 for ; Wed, 2 Apr 2003 16:11:31 -0500 (EST) Received: from 81-203-14-200.user.ono.com ([81.203.14.200]) by mta04.onolab.com (Netscape Messaging Server 4.15) with ESMTP id HCQIV708.617 for ; Wed, 2 Apr 2003 23:11:31 +0200 From: Juan Miguel To: pgsql-admin@postgresql.org Subject: Re: Speed & Memory Management Date: Wed, 2 Apr 2003 23:13:17 +0200 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304022313.17633.juanmime@ono.com> X-Spam-Status: No, hits=-9.0 required=5.0 tests=BAYES_10,QUOTED_EMAIL_TEXT,USER_AGENT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200304/26 X-Sequence-Number: 8181 > That would buy you absolutely nothing. char() is not faster than text. > Instead you would make everything slower because the system would > constantly have to pad and trim your values and it would bloat the storage > with the extra spaces. First, sorry about my english. Well ... but ... reading database theory books, you can see that fixed size records are "better" than variant size records. When the records are size fixed, inserts, updates and deletes can recalculate easier the position of the rest records in the pages. These books tell you that in general cases, variant record size tables (records that have variant type colums, for example) imply a lower performance in the system ... Why in postgresql these things don't matter ? Thanks.