At 09:28 AM 26/10/2004, Tom Lane wrote:
>I can't see what a search path would be good for.
Nothing at this stage.
>It seems like we still need some notion of a database's schema,
Yes.
>I'd be willing to jump this way if we can work out the
>default-tablespace inconsistencies that Bruce has on the open items
>list.
I'll have a look in the next 18 hours...
> * A GUC variable named something like default_tablespace that
> controls which TS objects are created in when there's
> no explicit TABLESPACE clause. The factory default for this
> would of course be pg_default. Otherwise it's settable just
> like any other GUC var.
Agree.
> * Get rid of TABLESPACE clause for CREATE SCHEMA, and
> pg_namespace.nsptablespace (ooops, another initdb).
Agree.
> * Need to define exactly what TABLESPACE clause for a database
> controls; location of its catalogs of course, but anything else?
Nothing else would be my call; make it like the tablespace on tables.
> * We could possibly say that a TABLESPACE clause attached to
> CREATE TABLE determines the default tablespace for indexes
> created by the same command;
This is a hard one. We need ALTER INDEX or STORE INDEX or whatever if we
can't nicely put each index in it's own tablespace. We're only talking PKs
aren't we? I'll have to think about this.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 03 5330 3172 | ___________ |
Http://www.rhyme.com.au | / \| | --________--
PGP key available upon request, | /
and from pgp.mit.edu:11371 |/
