public inbox for [email protected]  

help / color / mirror / Atom feed

From: Gavin Sherry <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Christopher Kings-Lynne <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: 8.0 beta status
Date: Sun, 15 Aug 2004 15:02:28 +1000 (EST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

On Sat, 14 Aug 2004, Bruce Momjian wrote:

> Christopher Kings-Lynne wrote:
> > > 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...
>
> I am confused.  You had:
>
> 	template1=# create tablespace blah location '/home/swm/tbl/tspc1/';
> 	CREATE TABLESPACE
> 	template1=# create table foo (i int) tablespace blah;
> 	CREATE TABLE
> 	template1=# create database foo tablespace blah;
> 	ERROR:  could not initialize database directory
> 	DETAIL:  Directory "/home/swm/tbl/data/pg_tblspc/17227/17230" already
> 	exists.
>
> but with CVS head I see:
>
> 	$ psql -a test </tmp/x
> 	create tablespace blah location '/bjm/tmp';
> 	CREATE TABLESPACE
> 	create table foo (i int) tablespace blah;
> 	CREATE TABLE
> 	create database foo tablespace blah;
> 	CREATE DATABASE

You need to create a condition where by the new database would have to
merge a table into its default database. If you did the above in the
template1 database, you would get the same effect.

I sent a (partial) fix for this, which included some documentation
improvements. However, I posed a question. *digs*

[PATCHES] CREATE DATABASE with tablespace fix

was the subject.

Gavin

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], [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