From: Andrew Sullivan <andrew@libertyrms.info>
To: pgsql-performance@postgresql.org
Subject: Re: Index File growing big.
Date: Wed, 26 Feb 2003 07:00:40 -0500
Message-ID: <20030226070040.C8814@mail.libertyrms.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0302261155430.691-100000@minxserver.philnet>
References: <Pine.LNX.4.33.0302261155430.691-100000@minxserver.philnet>
On Wed, Feb 26, 2003 at 11:56:48AM +0530, PRAGATI SAVAIKAR wrote:
>
> Can U please suggest some way to avoid the file getting created when we
> move the data file (along with the index files) to another partition.
Yes. Submit a patch which implements tablespaces ;-)
Seriously, there is no way to avoid this in the case where you are
moving the files by hand. The suggestions for how to move files
around note this.
If this is merely a disk-size problem, why not move the entire
postgres installation to another disk, and make a link to it. If you
still need to spread things across disks, you can move things which
don't change in size very much. A good candidate here is the WAL
(pg_xlog), since it grows to a predictable size. You even get a
performance benefit.
A
--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew@libertyrms.info> M2P 2A8
+1 416 646 3304 x110
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-performance@postgresql.org
Cc: andrew@libertyrms.info
Subject: Re: Index File growing big.
In-Reply-To: <20030226070040.C8814@mail.libertyrms.com>
References: <Pine.LNX.4.33.0302261155430.691-100000@minxserver.philnet> <20030226070040.C8814@mail.libertyrms.com>
* 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