From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Richard Emberson <emberson(at)phc(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Mapping tables to disk drives |
Date: | 2002-02-20 03:31:38 |
Message-ID: | 200202200331.g1K3Vcn02421@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Richard Emberson wrote:
> Bruce Momjian wrote:
>
> > Richard Emberson wrote:
> > > Are there any guides, references, etc. for helping someone:
> > > 1) know how to map a particular table to a particular disk drive (is it
> > > just symbolic links) and
> >
> > Yep, just symlinks. We know we need a better method. Also, as the
> > table grows, extent files for >1gb will also need to be symlinked.
> >
> > > 2) for what type of queries and table layout combination would it make
> > > sense to do so?
> >
> > First, pg_xlog/ should be on a separate drive. Then you can think about
> > moving indexes and tables to separate drives.
>
> I looked around the .../data directory. How does one map from index and
> table names
> to file names?
/contrib/oid2name.
> Also, I assume that when a extent file for >1Gb is created (by the DB as it
> is running)
> one must stop the DB, move the file, make a symbolic link to the moved file,
> and then
> restart the DB.
Yes, yuck.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Emberson | 2002-02-20 03:33:47 | Re: Mapping tables to disk drives |
Previous Message | mlw | 2002-02-20 03:25:25 | Re: data mining or statistical analysis with postgresql |