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 |
Views: | Raw Message | Whole Thread | 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.
--
Josh Berkus
josh(at)agliodbs(dot)com
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2002-10-08 22:51:11 | Re: [HACKERS] Large databases, performance |
Previous Message | Jeff Davis | 2002-10-08 20:47:33 | Re: ORDER BY and LIMIT questions in EXCEPTs |
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2002-10-08 22:51:11 | Re: [HACKERS] Large databases, performance |
Previous Message | Peter Eisentraut | 2002-10-08 21:42:18 | Re: v7.2.3 - tag'd, packaged ... need it checked ... |
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2002-10-08 22:51:11 | Re: [HACKERS] Large databases, performance |
Previous Message | Ron Johnson | 2002-10-08 17:42:20 | Re: CHAR, VARCHAR, TEXT (Was Large Databases) |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2002-10-08 23:36:40 | Re: CHAR, VARCHAR, TEXT (Was Large Databases) |
Previous Message | Charles Hauser | 2002-10-08 18:19:15 | Re: Problems Formulating a SELECT |