X-Original-To: pgsql-admin@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 864494762D7 for ; Tue, 1 Apr 2003 13:42:21 -0500 (EST) Received: from localhost.localdomain (unknown [65.217.53.66]) by postgresql.org (Postfix) with ESMTP id 2D0B2475AF8 for ; Tue, 1 Apr 2003 13:41:49 -0500 (EST) Received: from thorn.mmrd.com (thorn.mmrd.com [172.25.10.100]) by localhost.localdomain (8.12.5/8.12.5) with ESMTP id h31JI56P007797; Tue, 1 Apr 2003 14:18:05 -0500 Received: from gnvex001.mmrd.com (gnvex001.mmrd.com [192.168.3.55]) by thorn.mmrd.com (8.11.6/8.11.6) with ESMTP id h31IfRp11244; Tue, 1 Apr 2003 13:41:29 -0500 Received: from camel.mmrd.com ([172.25.5.213]) by gnvex001.mmrd.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id F3HTLP2Z; Tue, 1 Apr 2003 13:41:26 -0500 Subject: Re: Speed & Memory Management From: Robert Treat To: Kris Cc: pgsql-admin@postgresql.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 01 Apr 2003 13:41:27 -0500 Message-Id: <1049222487.13853.2110.camel@camel> Mime-Version: 1.0 X-Spam-Status: No, hits=-38.0 required=5.0 tests=BAYES_10,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_XIMIAN 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/7 X-Sequence-Number: 8162 Unless your application requires a 30 character limit at the logical level, use text. Robert Treat On Mon, 2003-03-31 at 17:08, Kris wrote: > Hello all. I am designing a database that will could potentially grow to > have millions of tuples associated with it. My thought is that because I > will likely have many updates/inserts/deletes occurring I should set each > column that requires text to a static ammount (ie using char(30) instead of > text). However, this looks to be a double edged sword, since selecting from > the db is my largest concern (with updates a very close second). When I > pull these values back out of the db, it seems I am going to have to trim > each returned value (when I pull a ten character string out of this field, > it returns the 10 char string as well as 20 whitespaces.). I am trying to > assign a weight to each of these scenarios and figure out which is the > lesser of the two evils. If anyone has a suggestion of how I may circumvent > this issue or which possibility may work best, it would be greatly > appreciated. Thanks >