Skip site navigation (1) Skip section navigation (2)

Re: Index File growing big.

From: Andrew Sullivan <andrew(at)libertyrms(dot)info>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Index File growing big.
Date: 2003-02-26 12:00:40
Message-ID: 20030226070040.C8814@mail.libertyrms.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-performance
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(at)libertyrms(dot)info>                              M2P 2A8
                                         +1 416 646 3304 x110


In response to

Responses

pgsql-performance by date

Next:From: daniel alvarezDate: 2003-02-26 13:04:39
Subject:
Previous:From: Rajesh Kumar MallahDate: 2003-02-26 07:29:23
Subject: Re: Index File growing big.

pgsql-hackers by date

Next:From: Michael MeskesDate: 2003-02-26 13:04:54
Subject: Re: Thread safe ecpg
Previous:From: Dave CramerDate: 2003-02-26 11:58:01
Subject: Re: autocommit off mode, how does it work?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group