X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id ABBAC11F6AD9 for ; Mon, 24 Apr 2006 15:16:11 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 53578-01-6 for ; Mon, 24 Apr 2006 15:15:52 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.logix-tt.com (unknown [212.211.145.186]) by postgresql.org (Postfix) with ESMTP id 9C63011F8DF9 for ; Mon, 24 Apr 2006 08:34:21 -0300 (ADT) Received: from kingfisher.intern.logix-tt.com (Ta21a.t.pppool.de [89.55.162.26]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.logix-tt.com (Postfix) with ESMTP id 27BA3656CD for ; Mon, 24 Apr 2006 13:35:24 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by kingfisher.intern.logix-tt.com (Postfix) with ESMTP id 45E8118148C83 for ; Mon, 24 Apr 2006 13:34:34 +0200 (CEST) Message-ID: <444CB7C9.8060307@logix-tt.com> Date: Mon, 24 Apr 2006 13:34:33 +0200 From: Markus Schaber Organization: Logical Tracking and Tracing International AG, Switzerland User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: PostgreSQL SQL List Subject: Re: Migrating a Database to a new tablespace References: <4444D607.1000309@logix-tt.com> <444CA2F5.4030705@logix-tt.com> <444CA971.3000505@logix-tt.com> In-Reply-To: <444CA971.3000505@logix-tt.com> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/160 X-Sequence-Number: 24969 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