Re: Migrating a Database to a new tablespace

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Markus Schaber <schabi(at)logix-tt(dot)com>
Cc: PostgreSQL SQL List <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Migrating a Database to a new tablespace
Date: 2006-04-25 00:15:53
Message-ID: 20060425001553.GM64695@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

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(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Mario Splivalo 2006-04-25 12:03:07 SELECTing into usertype, how to do it?
Previous Message Alvaro Herrera 2006-04-24 21:40:07 Re: "could not open file" issue