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.
>
> 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