From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200408150337.i7F3bTT27937@candle.pha.pa.us>
Subject: Re: 8.0 beta status
In-Reply-To: <25964.1091850874@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sat, 14 Aug 2004 23:37:29 -0400 (EDT)
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>,
	pgsql-hackers@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

Tom Lane wrote:
> > http://groups.google.com.au/groups?q=tablespaces+group:comp.databases.postgresql.hackers&hl=en&lr=&ie=UTF-8&group=comp.databases.postgresql.hackers&scoring=d&selm=4107211C.2050508%40familyhealth.com.au&rnum=5
> 
> I think the problem here is that we don't have a syntax for saying
> "my tablespace is the same as my database's default tablespace" or "my
> tablespace is the same as my schema's default tablespace", when there is
> an intermediate object (schema or table) that isn't using that
> tablespace. (Note that "TABLESPACE pg_default" does definitely not mean
> either of these.)
> 
> This is fixable with some special syntax but is it worth the trouble?

Seems we have to come up with some solution or dump/reload will not put
things back in the same place for certain unusual configurations.

Added to open items:

	* fix ambiguity for objects using default tablespaces

-- 
  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