Re: Index File growing big. - Mailing list pgsql-performance

From Jim Buttafuoco
Subject Re: Index File growing big.
Date
Msg-id 200302271234.h1RCYCF13164@contactbda.com
Whole thread Raw
In response to Re: Index File growing big.  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Responses Re: Index File growing big.
List pgsql-performance
All,

I was the person who submitted the patch.  I tried to a generic syntax.  I also tried to keep the tablespace concept
simple.  See my posting on HACKERS/GENERAL from a week or 2 ago about the syntax.  I am still interested in working on
this patch with others.  I have many system here that are 500+ gigabytes and growing.  It is a real pain to add more
disk space (I have to backup, drop database(s), rebuild raid set (I am using raid 10) and reload data).

Jim



> > > You should note that someone already has sent in a patch for
> tablespaces, it
> > > hasn't been acted on though - can't quite remember why.  Maybe we should
> > > resurrect it...
> >
> > It's been awhile, but my recollection is that the patch had restricted
> > functionality (which would be okay for a first cut) and it invented SQL
> > syntax that seemed to lock us into that restricted functionality
> > permanently (not so okay).  Details are fuzzy though...
>
> Well, I'll resurrect it and see if it can be improved.  Tablespaces seem to
> be a requested feature these days...
>
> Chris
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster





pgsql-performance by date:

Previous
From: "Shridhar Daithankar"
Date:
Subject: Re: Daily crash
Next
From: "Catalin"
Date:
Subject: Re: Daily crash