Re: Merge algorithms for large numbers of "tapes" - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Merge algorithms for large numbers of "tapes"
Date
Msg-id 8764mpo820.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: Merge algorithms for large numbers of "tapes"  ("Jonah H. Harris" <jonah.harris@gmail.com>)
List pgsql-hackers
"Jonah H. Harris" <jonah.harris@gmail.com> writes:

> On 3/7/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >
> > However, now that we've changed the code to prefer large numbers of tapes,
> > it's not at all clear that Algorithm D is still the right one to use. In
> > particular I'm looking at cascade merge, Algorithm 5.4.3C, which appears
> > to use significantly fewer passes when T is large. Do you want to try
> > that?
> 
> Guess we won't really know 'til it can be tested :)

It would also be interesting to allow multiple temporary areas to be declared
and try to spread tape files across the temporary areas. Ideally keeping input
and output tapes on separate drives.

-- 
greg



pgsql-hackers by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: pg_freespacemap question
Next
From: Josh Berkus
Date:
Subject: Re: PostgreSQL Anniversary Summit, Call for Contributions