From: Tom Lane <tgl@sss.pgh.pa.us>
To: Markus Schaber <schabi@logix-tt.com>
Cc: PostgreSQL SQL List <pgsql-sql@postgresql.org>
Subject: Re: Migrating a Database to a new tablespace
Date: Tue, 25 Apr 2006 14:13:18 -0400
Message-ID: <22840.1145988798@sss.pgh.pa.us> (raw)
In-Reply-To: <444E5359.5010704@logix-tt.com>
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>
Markus Schaber <schabi@logix-tt.com> writes:
> Tom Lane wrote:
>> Instead of assuming anything, why don't you look in the tablespace
>> directory and see what's there? A quick "ls -aR" would give more
>> information than guessing.
> There's plenty of stuff there, 8.8 Gigabytes in total. The question is
> how to determine if any of those files are still needed, and how to
> migrate them so I can drop that tablespace.
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.
regards, tom lane
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: tgl@sss.pgh.pa.us, schabi@logix-tt.com
Subject: Re: Migrating a Database to a new tablespace
In-Reply-To: <22840.1145988798@sss.pgh.pa.us>
* 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