From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, 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 22:48:25 |
Message-ID: | 877j4lsi12.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> > 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.
Would giving each tape its own file make it easier to allow multiple temporary
sort areas and allow optimizing to avoid seeking when multiple spindles area
available?
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-05-16 22:48:33 | Re: Compression and on-disk sorting |
Previous Message | Martijn van Oosterhout | 2006-05-16 21:58:02 | Re: Compression and on-disk sorting |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-05-16 22:48:33 | Re: Compression and on-disk sorting |
Previous Message | Martijn van Oosterhout | 2006-05-16 21:58:02 | Re: Compression and on-disk sorting |