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

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