bizgres - bizgres: Improve tuplesort.c to support variable merge order.

From: aparashar(at)pgfoundry(dot)org (User Aparashar)
To: pgsql-committers(at)postgresql(dot)org
Subject: bizgres - bizgres: Improve tuplesort.c to support variable merge order.
Date: 2006-03-03 22:11:38
Message-ID: 20060303221138.2B8691033806@pgfoundry.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Improve tuplesort.c to support variable merge order. The original coding
with fixed merge order (fixed number of "tapes") was based on obsolete
assumptions, namely that tape drives are expensive. Since our "tapes"
are really just a couple of buffers, we can have a lot of them given
adequate workspace. This allows reduction of the number of merge passes
with consequent savings of I/O during large sorts.

Simon Riggs with some rework by Tom Lane

Modified Files:
--------------
bizgres/postgresql/src/backend/optimizer/path:
costsize.c (r1.1.1.3.2.1 -> r1.3)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/backend/optimizer/path/costsize.c.diff?r1=1.1.1.3.2.1&r2=1.3)

Browse pgsql-committers by date

  From Date Subject
Next Message User Aparashar 2006-03-03 22:13:53 bizgres - bizgres: 1.
Previous Message User Aparashar 2006-03-03 22:09:43 bizgres - bizgres: Modify logtape.c so that the initial