Search Postgresql Archives

Re: B-tree index on a VARCHAR(4000) column

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ron Johnson <ron.l.johnson@xxxxxxx> writes:
> Based on LENGTH(offending_column), none of the values are more than 144 
> bytes in this 44.2M row table.  Even though VARCHAR is, by definition, 
> variable length, are there any internal design issues which would make 
> things more efficient if it were dropped to, for example, VARCHAR(256)?

No.

			regards, tom lane


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux