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&lr=&ie=UTF-8&group=comp.databases.postgresql.hackers&scoring=d&selm=Pine.LNX.4.58.0407281411470.17889%40linuxworld.com.au&rnum=4
>
> 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