Re: Index File growing big.

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: jim(at)contactbda(dot)com
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Sullivan <andrew(at)libertyrms(dot)info>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Index File growing big.
Date: 2003-03-06 20:18:56
Message-ID: 200303062018.h26KIu926973@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance


Yes, the issue was that it only had places for heap and index location,
not more generic.

I can work with a few folks to get this done. I think it can be done in
a few stages:

Decide on syntax/functionality
Update grammer to support it
Update system catalogs to hold information
Update storage manager to handle storage locations

If folks can decide on the first item, I can do the second and third
ones.

---------------------------------------------------------------------------

Jim Buttafuoco wrote:
> 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
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-03-06 20:22:43 Re: Partial index on date column
Previous Message Dave Page 2003-03-06 20:08:46 Re: Partial index on date column

Browse pgsql-performance by date

  From Date Subject
Next Message Bruce Momjian 2003-03-06 21:11:05 Re: OIDs as keys
Previous Message Josh Berkus 2003-03-06 19:12:07 Re: ISNULL performance tweaks