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 7A8AB5E40BB for ; Sat, 7 Aug 2004 00:54:36 -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 20066-03 for ; Sat, 7 Aug 2004 03:54:42 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 7F04E5E3F15 for ; Sat, 7 Aug 2004 00:54:33 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i773sZlE025965; Fri, 6 Aug 2004 23:54:37 -0400 (EDT) To: Christopher Kings-Lynne Cc: pgsql-hackers@postgresql.org Subject: Re: 8.0 beta status In-reply-to: <41130EAC.10102@familyhealth.com.au> References: <4027.1091750294@sss.pgh.pa.us> <4112DADB.6040906@familyhealth.com.au> <5415.1091754978@sss.pgh.pa.us> <41130EAC.10102@familyhealth.com.au> Comments: In-reply-to Christopher Kings-Lynne message dated "Fri, 06 Aug 2004 12:53:00 +0800" Date: Fri, 06 Aug 2004 23:54:34 -0400 Message-ID: <25964.1091850874@sss.pgh.pa.us> From: Tom Lane 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/319 X-Sequence-Number: 57291 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