Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 60DEC4760FA for ; Tue, 8 Oct 2002 18:45:35 -0400 (EDT) Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id B3852475F82 for ; Tue, 8 Oct 2002 18:45:34 -0400 (EDT) Received: from [216.135.165.74] (HELO lazarus) by davinci.ethosmedia.com (CommuniGate Pro SMTP 3.5.9) with ESMTP-TLS id 1776173; Tue, 08 Oct 2002 15:44:16 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Ron Johnson , pgsql-performance@postgresql.org Subject: Re: CHAR, VARCHAR, TEXT (Was Large Databases) Date: Tue, 8 Oct 2002 15:44:36 -0700 X-Mailer: KMail [version 1.4] References: <1034098940.1336.39.camel@haggis> In-Reply-To: <1034098940.1336.39.camel@haggis> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200210081544.36139.josh@agliodbs.com> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/66 X-Sequence-Number: 83 Ron, > > 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? > > ?????? In other words, if it ain't broke, don't fix it. --=20 Josh Berkus josh@agliodbs.com Aglio Database Solutions San Francisco