Thank you. Now I see that page consists of record pointers list build
from offset and length so there is no benefit of having constant
length here.
On Fri, Aug 19, 2011 at 17:03, Merlin Moncure mmonc...@gmail.com wrote:
On Fri, Aug 19, 2011 at 4:03 AM, Krzysztof Chodak
Is there any performance benefit of using constant size tuples?
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
On 8/19/2011 4:03 AM, Krzysztof Chodak wrote:
Is there any performance benefit of using constant size tuples?
If you are referring to varchar(80) vs text, then no, there is no benefit.
-Andy
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to
On Fri, Aug 19, 2011 at 4:03 AM, Krzysztof Chodak
krzysztof.cho...@gmail.com wrote:
Is there any performance benefit of using constant size tuples?
not really. If your tuple size is under a known maximum length, then
a toast table doesn't have to be created. that's a pretty minor
detail
