X-Original-To: pgsql-admin@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 8202847639D for ; Thu, 3 Apr 2003 14:48:17 -0500 (EST) Received: from localhost.localdomain (unknown [65.217.53.66]) by postgresql.org (Postfix) with ESMTP id 7A2124763D6 for ; Thu, 3 Apr 2003 14:47:50 -0500 (EST) Received: from thorn.mmrd.com (thorn.mmrd.com [172.25.10.100]) by localhost.localdomain (8.12.8/8.12.5) with ESMTP id h33KOskj018516; Thu, 3 Apr 2003 15:24:54 -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 h33Jlnx12684; Thu, 3 Apr 2003 14:47:50 -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 F3HTLY6N; Thu, 3 Apr 2003 14:47:48 -0500 Subject: Re: Speed & Memory Management From: Robert Treat To: Jodi Kanter Cc: Postgres Admin List In-Reply-To: <3E8C7BD0.3020006@virginia.edu> References: <3E8C7BD0.3020006@virginia.edu> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 03 Apr 2003 14:47:49 -0500 Message-Id: <1049399269.13798.5329.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/45 X-Sequence-Number: 8200 On Thu, 2003-04-03 at 13:22, Jodi Kanter wrote: > In response to the speed and memory management messages posted. Can > someone tell me if the varchar(N) data type also impedes performance by > padding with spaces? > Thank you, > Jodi > Well no since varchar doesn't pad spaces. Theoretically this does make it an improvement over char, although by this same theory it does have to do length checks on the input strings, which would slow things down versus text data types *in theory*. Don't forget also that a varchar(30) will _prevent_ strings longer than 30 chars, not truncate them. Robert Treat