Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 98F67475AFA for ; Tue, 8 Oct 2002 13:42:35 -0400 (EDT) Received: from lakemtao02.cox.net (lakemtao02.cox.net [68.1.17.243]) by postgresql.org (Postfix) with ESMTP id 0B5DE4759BD for ; Tue, 8 Oct 2002 13:42:35 -0400 (EDT) Received: from localhost.localdomain ([68.11.66.83]) by lakemtao02.cox.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with ESMTP id <20021008174235.DSTC12192.lakemtao02.cox.net@localhost.localdomain> for ; Tue, 8 Oct 2002 13:42:35 -0400 Subject: Re: CHAR, VARCHAR, TEXT (Was Large Databases) From: Ron Johnson To: pgsql-performance@postgresql.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 08 Oct 2002 12:42:20 -0500 Message-Id: <1034098940.1336.39.camel@haggis> Mime-Version: 1.0 X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/65 X-Sequence-Number: 82 On Tue, 2002-10-08 at 10:33, Josh Berkus wrote: > Ron, Shridhar, > > Maybe I missed something on this thread, but can either of you give me > an example of a real database where the PostgreSQL approach of "all > strings are TEXT" versus the more traditional CHAR implementation have > resulted in measurable performance loss? ?????? > Otherwise, this discussion is rather academic ... -- +------------------------------------------------------------+ | Ron Johnson, Jr. mailto:ron.l.johnson@cox.net | | Jefferson, LA USA http://members.cox.net/ron.l.johnson | | | | "they love our milk and honey, but preach about another | | way of living" | | Merle Haggard, "The Fighting Side Of Me" | +------------------------------------------------------------+