From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
---|---|
To: | Chairudin Sentosa <chai(at)prima(dot)net(dot)id>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Suggestion to split /data/base directory |
Date: | 2000-02-14 04:41:35 |
Message-ID: | 3.0.1.32.20000213204135.01704ec0@mail.pacifier.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 09:47 AM 2/14/00 +0700, Chairudin Sentosa wrote:
>My suggestion is to split files into 4 different directories:
>/data/base/mydb/data
>/data/base/mydb/index
>/data/base/mydb/dictionary
>/data/base/mydb/tmp
My preference would be for a simplistic "create tablespace" construct,
so location information could be captured within the database itself.
We've had discussions about this in the past and there seems to be
some recognition that the ability to spread stuff around disk drives
might be useful. I mean, all those commercial sites that do it after
measuring their bottlenecks can't ALL be wrong, right?
>
>So I can put each directory on different hardisk, so I can
>have 4 hardisks for 'mydb' database.
You can already do this in an ugly fashion, by moving individual
files via links (ln -s). ls *idx*, that kind of thing to find
your index tables (if you suffix them with "idx", then move and
ln to them.
>
>Is it doable and a good idea?
Doable, but IMO a bad idea because it lowers the motivation for doing
a relatively simple CREATE TABLESPACE hack that gives even more
flexibility, and allows the db user to query where their tables
are stored within the db rather than depend on "ls".
- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.
From | Date | Subject | |
---|---|---|---|
Next Message | Don Baccus | 2000-02-14 04:57:11 | Re: [HACKERS] Solution for LIMIT cost estimation |
Previous Message | Chris Bitmead | 2000-02-14 04:32:31 | Re: [HACKERS] Solution for LIMIT cost estimation |