From: Josh Berkus <josh@agliodbs.com>
To: Ron Johnson <ron.l.johnson@cox.net>
To: pgsql-performance@postgresql.org
Subject: Re: CHAR, VARCHAR, TEXT (Was Large Databases)
Date: Tue, 8 Oct 2002 15:44:36 -0700
Message-ID: <200210081544.36139.josh@agliodbs.com> (raw)
In-Reply-To: <1034098940.1336.39.camel@haggis>
References: <web-1775407@davinci.ethosmedia.com>
<1034098940.1336.39.camel@haggis>
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.
--
Josh Berkus
josh@agliodbs.com
Aglio Database Solutions
San Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com, ron.l.johnson@cox.net, pgsql-performance@postgresql.org
Subject: Re: CHAR, VARCHAR, TEXT (Was Large Databases)
In-Reply-To: <200210081544.36139.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox