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

From Ron Johnson
Subject [GENERAL] B-tree index on a VARCHAR(4000) column
Date
Msg-id 780beb7c-94f3-fed9-9959-73b725632949@cox.net
Whole thread Raw
Responses Re: [GENERAL] B-tree index on a VARCHAR(4000) column
Re: [GENERAL] B-tree index on a VARCHAR(4000) column
List pgsql-general
Hi,

v 9.2.7

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)?

(I don't have access to the source code or to development boxes, so can't 
just test this on my own.)

Thanks,

-- 
World Peace Through Nuclear Pacification



-- 
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: Michael Paquier
Date:
Subject: Re: [GENERAL] pg_rewind issue
Next
From: Craig Ringer
Date:
Subject: Re: [GENERAL] BDR, wal segment has been removed, is it possible move forward?