From: Bruce Momjian <pgman@candle.pha.pa.us>
To: jim@contactbda.com
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Sullivan <andrew@libertyrms.info>
Cc: pgsql-performance@postgresql.org
Subject: Re: Index File growing big.
Date: Thu, 6 Mar 2003 15:18:56 -0500 (EST)
Message-ID: <200303062018.h26KIu926973@candle.pha.pa.us> (raw)
In-Reply-To: <200302271234.h1RCYCF13164@contactbda.com>
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@postgresql.org so that your
> message can get through to the mailing list cleanly
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
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: pgman@candle.pha.pa.us, jim@contactbda.com, chriskl@familyhealth.com.au, tgl@sss.pgh.pa.us, andrew@libertyrms.info
Subject: Re: Index File growing big.
In-Reply-To: <200303062018.h26KIu926973@candle.pha.pa.us>
References: <200302271234.h1RCYCF13164@contactbda.com> <200303062018.h26KIu926973@candle.pha.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