Skip site navigation (1) Skip section navigation (2)

pgsql: Rename MaxTupleSize to MaxHeapTupleSize to clarify that it's not

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Rename MaxTupleSize to MaxHeapTupleSize to clarify that it's not
Date: 2007-02-05 04:22:18
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
Log Message:
Rename MaxTupleSize to MaxHeapTupleSize to clarify that it's not meant to
describe the maximum size of index tuples (which is typically AM-dependent
anyway); and consequently remove the bogus deduction for "special space"
that was built into it.

Adjust TOAST_TUPLE_THRESHOLD and TOAST_MAX_CHUNK_SIZE to avoid wasting two
bytes per toast chunk, and to ensure that the calculation correctly tracks any
future changes in page header size.  The computation had been inaccurate in a
way that didn't cause any harm except space wastage, but future changes could
have broken it more drastically.

Fix the calculation of BTMaxItemSize, which was formerly computed as 1 byte
more than it could safely be.  This didn't cause any harm in practice because
it's only compared against maxalign'd lengths, but future changes in the size
of page headers or btree special space could have exposed the problem.

initdb forced because of change in TOAST_MAX_CHUNK_SIZE, which alters the
storage of toast tables.

Modified Files:
        heapam.c (r1.226 -> r1.227)
        hio.c (r1.64 -> r1.65)
        vacuum.c (r1.344 -> r1.345)
        htup.h (r1.89 -> r1.90)
        nbtree.h (r1.109 -> r1.110)
        tuptoaster.h (r1.31 -> r1.32)
        c.h (r1.217 -> r1.218)
        catversion.h (r1.379 -> r1.380)

pgsql-committers by date

Next:From: Andrew DunstanDate: 2007-02-05 15:22:18
Subject: pgsql: Pass modern COPY syntax to backend, since copy (query) does not
Previous:From: Tom LaneDate: 2007-02-04 20:00:49
Subject: pgsql: Don't MAXALIGN in the checks to decide whether a tuple is over

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group