| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| 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 18:13:18 |
| Message-ID: | 22840.1145988798@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Markus Schaber <schabi(at)logix-tt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ray Madigan | 2006-04-26 02:50:59 | Linked List |
| Previous Message | Markus Schaber | 2006-04-25 16:50:33 | Re: Migrating a Database to a new tablespace |