Skip site navigation (1) Skip section navigation (2)

Re: Failed CLUSTER seems to leave files behind

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Antti Salmela <asalmela(at)iki(dot)fi>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Failed CLUSTER seems to leave files behind
Date: 2005-11-03 15:03:16
Message-ID: 22050.1131030196@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Antti Salmela <asalmela(at)iki(dot)fi> writes:
> Failed CLUSTER due to insufficient disk space seems to leave temporary files
> behind at least on 7.4.7.

What was the "failure" exactly?  If you ran out of disk space for the
data files, I'd have expected it to reclaim the temp files.  On the
other hand, running out of disk space for WAL would lead to a
database-wide PANIC, and there's no mechanism for getting rid of
unreferenced files after a PANIC.  (IIRC this is intentional ---
deleting files that we think aren't used seems too risky.)

This is one of several reasons for keeping WAL and data on separate
disks ...

> Is it safe to remove these files manually?

Yeah, if you're sure they correspond to no pg_class.relfilenode entry.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Bernhard WeisshuhnDate: 2005-11-03 15:12:33
Subject: BUG #2019: tsearch2-related coredump
Previous:From: IvanDate: 2005-11-03 14:33:05
Subject: Re: pg_dumpall bug & feature request

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group