Date: Mon, 24 Apr 2006 19:15:53 -0500
From: "Jim C. Nasby" <jnasby@pervasive.com>
To: Markus Schaber <schabi@logix-tt.com>
Cc: PostgreSQL SQL List <pgsql-sql@postgresql.org>
Subject: Re: Migrating a Database to a new tablespace
Message-ID: <20060425001553.GM64695@pervasive.com>
References: <4444D607.1000309@logix-tt.com> <444CA2F5.4030705@logix-tt.com>
	<444CA971.3000505@logix-tt.com> <444CB7C9.8060307@logix-tt.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <444CB7C9.8060307@logix-tt.com>
User-Agent: Mutt/1.5.11

That means that the tablespace directory isn't empty.

On Mon, Apr 24, 2006 at 01:34:33PM +0200, Markus Schaber wrote:
> Hello,
> 
> I now pulled the plug, migrated all databases via "create database ...
> tempate olddatabase tablespace newts" to new tablespaces, one for each
> database, and dropped all old databases that contained references to the
> tablespace. Pgadmin3 also shows that the tablespace is not referenced by
> anything.
> 
> But I cannot drop it, I get the following message:
> 
> postgres=# drop TABLESPACE foo;
> ERROR:  tablespace "foo" is not empty
> 
> 
> It seems that the whole tablespace thing is not yet 100% waterproof,
> good that this did happen on a developer machine, and not on a
> production machine.
> 
> Thanks for your patience,
> Markus
> 
> -- 
> Markus Schaber | Logical Tracking&Tracing International AG
> Dipl. Inf.     | Software Development GIS
> 
> Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
> 
>                http://archives.postgresql.org
> 

-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461