Re: [GENERAL] B-tree index on a VARCHAR(4000) column - Mailing list pgsql-general

From Tom Lane
Subject Re: [GENERAL] B-tree index on a VARCHAR(4000) column
Date
Msg-id 19165.1504871772@sss.pgh.pa.us
Whole thread Raw
In response to [GENERAL] B-tree index on a VARCHAR(4000) column  (Ron Johnson <ron.l.johnson@cox.net>)
Responses Re: [GENERAL] B-tree index on a VARCHAR(4000) column  (John Turner <fenwayriffs@gmail.com>)
List pgsql-general
Ron Johnson <ron.l.johnson@cox.net> 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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: hamann.w@t-online.de
Date:
Subject: Re: [GENERAL] column names query
Next
From: Merlin Moncure
Date:
Subject: Re: [GENERAL] B-tree index on a VARCHAR(4000) column