To: Markus Schaber <schabi@logix-tt.com>
cc: PostgreSQL SQL List <pgsql-sql@postgresql.org>
Subject: Re: Migrating a Database to a new tablespace 
In-reply-to: <44508A44.4090909@logix-tt.com> 
References: <200604261635.k3QGZdB06325@candle.pha.pa.us>
	<44508A44.4090909@logix-tt.com>
Comments: In-reply-to Markus Schaber <schabi@logix-tt.com>
	message dated "Thu, 27 Apr 2006 11:09:24 +0200"
Date: Thu, 27 Apr 2006 11:06:09 -0400
Message-ID: <11235.1146150369@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Markus Schaber <schabi@logix-tt.com> writes:
> Bruce Momjian wrote:
>> I have work someone did in the past.  I just need to be updated to deal
>> with tablespaces.
>> 
>> ftp://candle.pha.pa.us/pub/postgresql/mypatches/checkfile.*

> It looks nice, but I would not like automatic deletion (or only optional
> or configurable), there might be valid reasons for "alien" files to
> exist. (README files for admins to communicate what this directory is
> used for, MacOS ressource forks, Reiser4 special files etc...)

> What about putting the identification code in a set returning function
> or view that can be called by the admin.

Yeah, one thing I never liked about the previously proposed patches was
that they were tied to postmaster start/restart.  It'd be better to have
an external tool that could be invoked on demand.  Maybe something close
to oid2name.

			regards, tom lane