Hi,
Le 26 juin 09 à 05:20, Jeremy Kerr a écrit :
Unfortunately, the cases with lots of padding spaces are probably
much less probable than the cases with fewer. It would be unpleasant
for example if this patch resulted in a severe performance
degradation for a "canonical" example of char(n) being used properly,
such as char(2) for US state abbreviations.
Yep, makes sense. The other consideration is stock-ticker symbols, I
assume they may also be stored in CHAR(small n) columns.
Could this optimisation only kicks in when n is "big enough"?
I'm don't know if this part of the code knows the typmod...
Regards,
--
dim
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
