From: Markus Schaber <schabi@logix-tt.com>
To: PostgreSQL SQL List <pgsql-sql@postgresql.org>
Subject: Re: Migrating a Database to a new tablespace
Date: Wed, 26 Apr 2006 10:10:26 +0200
Message-ID: <444F2AF2.4070906@logix-tt.com> (raw)
In-Reply-To: <22840.1145988798@sss.pgh.pa.us>
References: <4444D607.1000309@logix-tt.com>
<444CA2F5.4030705@logix-tt.com>
<444CA971.3000505@logix-tt.com>
<444CB7C9.8060307@logix-tt.com>
<20060425001553.GM64695@pervasive.com>
<444E208C.20901@logix-tt.com>
<19435.1145978379@sss.pgh.pa.us>
<444E5359.5010704@logix-tt.com>
<22840.1145988798@sss.pgh.pa.us>
Hi, Tom,
Tom Lane wrote:
> Match the subdirectory names against pg_database.oid --- any subdir that
> doesn't correspond to any live entry in pg_database is junk and can be
> flushed. Within a valid database's subdirectory, match the file names
> to that database's pg_class.relfilenode (not oid!) to see if any of them
> are live.
Ah, that did it. Both "top level" Directories are not found in
pg_database.oid, so they are leftovers from dropped databases. I deleted
them, and then the tablespace could be dropped.
Thanks a lot, Tom.
As I said the leftovers are likely to be caused by hard kills and
backend crashes, so I would not go into deeper analysis, but maybe the
finding and possibly removing of such leftovers should be half-automated
to assist server admins.
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
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: pgsql-sql@postgresql.org
Cc: schabi@logix-tt.com
Subject: Re: Migrating a Database to a new tablespace
In-Reply-To: <444F2AF2.4070906@logix-tt.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox