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: Thu, 27 Apr 2006 10:53:17 +0200
Message-ID: <4450867D.9060908@logix-tt.com> (raw)
In-Reply-To: <18451.1146069195@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>
<444F2AF2.4070906@logix-tt.com>
<18451.1146069195@sss.pgh.pa.us>
Hi, Tom,
Tom Lane wrote:
>>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.
>
> It's been discussed. Personally I'm afraid of the idea of automatically
> deleting files that seem unreferenced, but having a tool to find them
> for manual deletion isn't a bad idea.
I also don't like the idea of full automated deletion, that's why I
wrote half-automated.
I thought of a tool that enumarates suspective files. Then admins can
look at the mtime/atime, or move them away and try what happens, or even
pipe the output to "xargs rm -rf" if they want.
Thanks,
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: <4450867D.9060908@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