From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Rod Taylor <pg(at)rbt(dot)ca>, "Bort, Paul" <pbort(at)tmwsystems(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Compression and on-disk sorting |
Date: | 2006-05-16 21:58:02 |
Message-ID: | 20060516215802.GN976@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Tue, May 16, 2006 at 04:50:22PM -0500, Jim C. Nasby wrote:
> > I had a look at this. At first glance it doesn't seem too hard, except
> > the whole logtape process kinda gets in the way. If it wern't for the
> > mark/restore it'd be trivial. Might take a stab at it some time, if I
> > can think of a way to handle the seeking...
>
> Oh, do we need to randomly seek? Is that how we switch from one tape to
> another?
Not seek, mark/restore. As the code describes, sometimes you go back a
tuple. The primary reason I think is for the final pass, a merge sort
might read the tuples multiple times, so it needs to support it there.
> It might be easier to switch to giving each tape it's own file...
I don't think it would make much difference. OTOH, if this turns out to
be a win, the tuplestore could have the same optimisation.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2006-05-16 22:48:25 | Re: Compression and on-disk sorting |
Previous Message | Jim C. Nasby | 2006-05-16 21:50:22 | Re: Compression and on-disk sorting |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2006-05-16 22:48:25 | Re: Compression and on-disk sorting |
Previous Message | Jim C. Nasby | 2006-05-16 21:50:22 | Re: Compression and on-disk sorting |