Re: default_index_tablespace?

From: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
To: Kelly Burkhart <kelly(dot)burkhart(at)gmail(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Alexander M(dot) Pravking" <fduch(at)antar(dot)bryansk(dot)ru>, pgsql-general(at)postgresql(dot)org
Subject: Re: default_index_tablespace?
Date: 2005-12-02 22:42:49
Message-ID: 20051202224248.GT13642@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

TODO?

%Add default_index_tablespace GUC and database parameter.

On Thu, Dec 01, 2005 at 11:48:28AM -0600, Kelly Burkhart wrote:
> On 12/1/05, Alexander M. Pravking <fduch(at)antar(dot)bryansk(dot)ru> wrote:
> >
> > PostgreSQL 8.0 brought a great tablespaces feature. However, it's still
> > a real pain for one who wants to separate tables and indices to different
> > tablespaces: he has to do it manually, explicitely specifying tablespace
> > for each index.
> >
> > Thus, I think it would be handy to have "default_index_tablespace" server
> > variable. Any thoughts?
>
>
> We would use such a thing. Our databases use three partitions: log, data,
> index. We currently create our databases like:
>
> CREATE DATABASE dbname OWNER owner TABLESPACE tsname;
>
> We then specify another index tablespace on index creation (which really
> isn't that difficult).
>
>
> Adding an INDEX_TABLESPACE option to CREATE DATABASE might be worthwhile if
> what we have done is typical. Or if pg maintainers want to suggest this
> usage as sensible.
>
> -K

--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-12-02 22:49:22 Re: Numeric 508 datatype
Previous Message Bruce Momjian 2005-12-02 22:41:34 Re: Numeric 508 datatype