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 16:36:40 -0700
Message-ID: <200210081636.40713.josh@agliodbs.com> (raw)
In-Reply-To: <1034119771.1365.154.camel@haggis>
References: <web-1775407@davinci.ethosmedia.com>
<200210081544.36139.josh@agliodbs.com>
<1034119771.1365.154.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.
>
> Well, does Really Slow Performance qualify as "broke"?
That's what I was asking. Can you explain where your slow performance is
attibutable to the CHAR implementation issues? I missed that, if it was
explained earlier in the thread.
--
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: <200210081636.40713.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