possible bug: orphaned files left after immediate shutdown during DDL

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: possible bug: orphaned files left after immediate shutdown during DDL
Date: 2011-02-10 03:37:06
Message-ID: 1297309026.11375.7.camel@jdavis-ux.asterdata.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


Case:

BEGIN;
CREATE TABLE foo AS SELECT generate_series(1,1000);
CHECKPOINT;
SELECT relfilenode FROM pg_class WHERE relname='foo';

Let's say that returns 23456. Send the postmaster a SIGQUIT (immediate
shutdown), and then restart. The file 23456 is still in the filesystem,
but there's no record in pg_class for it. I don't see any obvious path
where it will be removed, so it looks like it will just stay there
forever.

My question is: is this a conscious decision to be paranoid during
recovery, or is this a bug? Or is there some reason that properly
determining which files should be removed at recovery time is
challenging?

Regards,
Jeff Davis

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2011-02-10 03:37:36 Re: [Fwd: ERROR: cannot extract system attribute from minimal tuple]
Previous Message Alvaro Herrera 2011-02-10 03:11:48 Re: [Fwd: ERROR: cannot extract system attribute from minimal tuple]