bizgres - bizgres: Modify logtape.c so that the initial

From: aparashar(at)pgfoundry(dot)org (User Aparashar)
To: pgsql-committers(at)postgresql(dot)org
Subject: bizgres - bizgres: Modify logtape.c so that the initial
Date: 2006-03-03 22:09:43
Message-ID: 20060303220944.9A5EA1033806@pgfoundry.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Modify logtape.c so that the initial LogicalTapeSetCreate call only
allocates the control data. The per-tape buffers are allocated only
on first use. This saves memory in situations where tuplesort.c
overestimates the number of tapes needed (ie, there are fewer runs
than tapes). Also, this makes legitimate the coding in inittapes()
that includes tape buffer space in the maximum-memory calculation:
when inittapes runs, we've already expended the whole allowed memory
on tuple storage, and so we'd better not allocate all the tape buffers
until we've flushed some tuples out of memory.
Work by Simon and Tom.

Modified Files:
--------------
bizgres/postgresql/src/backend/utils/sort:
logtape.c (r1.1.1.2.2.1 -> r1.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/backend/utils/sort/logtape.c.diff?r1=1.1.1.2.2.1&r2=1.2)

Browse pgsql-committers by date

  From Date Subject
Next Message User Aparashar 2006-03-03 22:11:38 bizgres - bizgres: Improve tuplesort.c to support variable merge order.
Previous Message Bruce Momjian 2006-03-03 22:02:08 pgsql: Rename Online Backup to Continuous Archiving.