From: Tom Lane <tgl@sss.pgh.pa.us>
To: scott.marlowe <scott.marlowe@ihs.com>
Cc: hal <hal@cc.usu.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: Multiple disks
Date: Fri, 09 Apr 2004 12:33:02 -0400
Message-ID: <26548.1081528382@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.33.0404090906570.11444-100000@css120.ihs.com>
References: <Pine.LNX.4.33.0404090906570.11444-100000@css120.ihs.com>
"scott.marlowe" <scott.marlowe@ihs.com> writes:
> The next way is to individually link thinks like indexes onto other
> volumes. The procedure is basically, create the index, figure out which
> file in $PGDATA/base/oidofyourdbhere is the index, shut down postgresql,
> copy to file elsewhere, softlink it, restart apache. This setup will not
> survive reindexing or dropping / recreating the index.
It should also be noted that this hack doesn't cope well with tables or
indexes exceeding 1Gb. You'd have to separately symlink each segment,
and deal with creating new links every time the table/index grows past
another 1Gb boundary.
Tablespaces will be a lot nicer when we have them. For now, a RAID
array is definitely the best bet.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, scott.marlowe@ihs.com, hal@cc.usu.edu
Subject: Re: Multiple disks
In-Reply-To: <26548.1081528382@sss.pgh.pa.us>
References: <Pine.LNX.4.33.0404090906570.11444-100000@css120.ihs.com> <26548.1081528382@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox