public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Christopher Kings-Lynne <[email protected]>
Cc: [email protected]
Subject: Re: 8.0 beta status
Date: Fri, 06 Aug 2004 23:54:34 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
Christopher Kings-Lynne <[email protected]> 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&a...
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&a...
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
view thread (16+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: 8.0 beta status
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox