pgsql: Modify aset.c to track the next intended block allocation size

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Modify aset.c to track the next intended block allocation size
Date: 2006-11-08 19:27:24
Message-ID: 20061108192724.371139FB26B@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Modify aset.c to track the next intended block allocation size explicitly.
The former coding relied on the actual allocated size of the last block,
which made it behave strangely if the first allocation in a context was
larger than ALLOC_CHUNK_LIMIT: subsequent allocations would be referenced
to that and not to the intended series of block sizes. Noted while
studying a memory wastage gripe from Tatsuo.

Modified Files:
--------------
pgsql/src/backend/utils/mmgr:
aset.c (r1.68 -> r1.69)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/mmgr/aset.c.diff?r1=1.68&r2=1.69)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2006-11-08 20:12:05 pgsql: Change Windows rename and unlink substitutes so that they time
Previous Message Tom Lane 2006-11-08 19:24:38 pgsql: Tweak accumArrayResult() to double the size of its working arrays