X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D5A005E46C1 for ; Fri, 13 Aug 2004 01:09:06 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 23705-02 for ; Fri, 13 Aug 2004 04:09:10 +0000 (GMT) Received: from houston.familyhealth.com.au (fhnet.arach.net.au [203.22.197.21]) by svr1.postgresql.org (Postfix) with ESMTP id 8269C5E46BF for ; Fri, 13 Aug 2004 01:08:59 -0300 (ADT) Received: from [192.168.0.40] (work-40.internal [192.168.0.40]) by houston.familyhealth.com.au (8.12.9p1/8.12.9) with ESMTP id i7D48uUi065805; Fri, 13 Aug 2004 12:08:56 +0800 (WST) (envelope-from chriskl@familyhealth.com.au) Message-ID: <411C402E.2070306@familyhealth.com.au> Date: Fri, 13 Aug 2004 12:14:38 +0800 From: Christopher Kings-Lynne User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruce Momjian Cc: Tom Lane , pgsql-hackers@postgresql.org Subject: Re: 8.0 beta status References: <200408130403.i7D43tv13820@candle.pha.pa.us> In-Reply-To: <200408130403.i7D43tv13820@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/760 X-Sequence-Number: 57729 The other tablespace problem is if you drop a tablespace that schema in another db uses, it's broken still I think. Chris Bruce Momjian wrote: > Where are we on this? > > --------------------------------------------------------------------------- > > Tom Lane wrote: > >>Christopher Kings-Lynne writes: >> >>>>Yeah, those are all bug fixes and okay for post-beta I think. But which >>>>two tablespace failures are you thinking of exactly? The last couple >>>>weeks have been a bit of a blur for me... >> >>>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=Pine.LNX.4.58.0407281411470.17889%40linuxworld.com.au&rnum=4 >> >>Okay, this is a the-error-message-could-be-better gripe. Fair enough, >>but it's not top of my priority list ... >> >> >>>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? >> >> regards, tom lane >> >>---------------------------(end of broadcast)--------------------------- >>TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org >> > >