Re: CHAR, VARCHAR, TEXT (Was Large Databases)

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>, pgsql-performance(at)postgresql(dot)org
Subject: Re: CHAR, VARCHAR, TEXT (Was Large Databases)
Date: 2002-10-08 23:36:40
Message-ID: 200210081636.40713.josh@agliodbs.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-performance pgsql-sql


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(at)agliodbs(dot)com
Aglio Database Solutions
San Francisco

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2002-10-09 00:10:04 Re: firstest doubts...
Previous Message Martijn van Oosterhout 2002-10-08 22:51:11 Re: [HACKERS] Large databases, performance

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-10-09 00:07:30 Re: inline newNode()
Previous Message Laurette Cisneros 2002-10-08 23:34:02 pgsql 7.2.3 crash

Browse pgsql-performance by date

  From Date Subject
Next Message Josh Berkus 2002-10-09 03:46:12 What does this tell me?
Previous Message Martijn van Oosterhout 2002-10-08 22:51:11 Re: [HACKERS] Large databases, performance

Browse pgsql-sql by date

  From Date Subject
Next Message Rudi Starcevic 2002-10-09 00:20:24 Table Rule
Previous Message Josh Berkus 2002-10-08 22:44:36 Re: CHAR, VARCHAR, TEXT (Was Large Databases)