Re: [GENERAL] Physical Database Configuration - Mailing list pgsql-hackers

From johnnnnnn
Subject Re: [GENERAL] Physical Database Configuration
Date
Msg-id 20030625195624.GG36005@performics.com
Whole thread Raw
In response to Re: [GENERAL] Physical Database Configuration  ("Andrew Dunstan" <andrew@dunslane.net>)
Responses Re: [GENERAL] Physical Database Configuration
List pgsql-hackers
On Wed, Jun 25, 2003 at 10:30:31AM -0500, Andrew Dunstan wrote:
> DB2 looks good. I have horrid, horrid memories of wrestling with the
> Oracle "extent" madness.

I do think that it's worth providing additional access points to
tablespaces, though. That is, it would make sense to me to allow
"CREATE INDEX indexname IN spacename", instead of attaching an
indexspace to a table.

This is especially true with postgresql, since i've seen more than one
proposal for multi-table indices. If we're spacing indices based on
the table, it's unclear where a given multi-table index should go.

It would also allow for other flexibilities, like putting join indices
(on foreign keys) in one tablespace, with indices for aggregation or
sorting in another tablespace.

So, my vote, as a non-code-contributing member, would be for a
DB2-style syntax, without the "INDEX IN" and "LONG IN" extensions, but
with the ability to put indices explicitly into a tablespace.

-johnnnnnn



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Two weeks to feature freeze
Next
From: greg@turnstep.com
Date:
Subject: Re: Updating psql for features of new FE/BE protocol