From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, 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-17 21:44:22 |
Message-ID: | 873bf8qqbt.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
"Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> On Wed, May 17, 2006 at 12:55:53PM -0400, Greg Stark wrote:
> >
> > "Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> >
> > > Only if those spindles weren't all in a single RAID array and if we went
> > > through the trouble of creating all the machinery so you could tell
> > > PostgreSQL where all those spindles were mounted in the filesystem.
> >
> > I think the way you do this is simply by documenting that the admin should
> > create precisely one temp area per physical spindle (or raid array).
>
> And you still need some way to tell PostgreSQL about all of that.
No, my point was that you tell Postges how many spindles you have and where to
find them by creating precisely one temp area on each spindle. It then knows
that it should strive to maximize sequential reads within one temp area and
expect switching between temp areas (which represent multiple spindles) to be
better than multiplexing multiple tapes within a single temp area (which
represents a single spindle).
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-05-17 21:50:59 | Re: [HACKERS] .pgpass file and unix domain sockets |
Previous Message | Hannu Krosing | 2006-05-17 21:18:19 | Re: PL/pgSQL 'i = i + 1' Syntax |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-05-17 21:50:59 | Re: [HACKERS] .pgpass file and unix domain sockets |
Previous Message | Jim C. Nasby | 2006-05-17 20:20:07 | Re: Compression and on-disk sorting |