Skip site navigation (1) Skip section navigation (2)

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 22:44:36
Message-ID: 200210081544.36139.josh@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackerspgsql-performancepgsql-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.

-- 
Josh Berkus
josh(at)agliodbs(dot)com
Aglio Database Solutions
San Francisco

In response to

Responses

pgsql-performance by date

Next:From: Martijn van OosterhoutDate: 2002-10-08 22:51:11
Subject: Re: [HACKERS] Large databases, performance
Previous:From: Ron JohnsonDate: 2002-10-08 17:42:20
Subject: Re: CHAR, VARCHAR, TEXT (Was Large Databases)

pgsql-hackers by date

Next:From: Martijn van OosterhoutDate: 2002-10-08 22:51:11
Subject: Re: [HACKERS] Large databases, performance
Previous:From: Peter EisentrautDate: 2002-10-08 21:42:18
Subject: Re: v7.2.3 - tag'd, packaged ... need it checked ...

pgsql-sql by date

Next:From: Josh BerkusDate: 2002-10-08 23:36:40
Subject: Re: CHAR, VARCHAR, TEXT (Was Large Databases)
Previous:From: Charles HauserDate: 2002-10-08 18:19:15
Subject: Re: Problems Formulating a SELECT

pgsql-general by date

Next:From: Martijn van OosterhoutDate: 2002-10-08 22:51:11
Subject: Re: [HACKERS] Large databases, performance
Previous:From: Jeff DavisDate: 2002-10-08 20:47:33
Subject: Re: ORDER BY and LIMIT questions in EXCEPTs

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group