X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6D9F23A2D9C for ; Sat, 15 Jan 2005 22:48:18 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 64371-10 for ; Sat, 15 Jan 2005 22:48:14 +0000 (GMT) Received: from echo.computel.nl (mail.nederland.net [83.137.20.15]) by svr1.postgresql.org (Postfix) with ESMTP id 588703A2D99 for ; Sat, 15 Jan 2005 22:48:15 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by echo.computel.nl (Postfix) with SMTP id 00ED23F87; Sat, 15 Jan 2005 23:48:16 +0100 (CET) X-AV-Checked: Sat Jan 15 23:48:16 2005 www.nederland.net Received: from balefirehome (balefire.demon.nl [212.238.240.59]) by echo.computel.nl (Postfix) with ESMTP id 4B9153F73; Sat, 15 Jan 2005 23:48:15 +0100 (CET) Message-ID: <005601c4fb54$581d0ce0$64c8a8c0@balefirehome> From: "Sander Steffann" To: "Tom Lane" Cc: References: <003201c4fb14$b7377840$64c8a8c0@balefirehome> <10233.1105812077@sss.pgh.pa.us> <005001c4fb50$8ae67110$64c8a8c0@balefirehome> Subject: Re: Less available diskspace after crashed CLUSTER Date: Sat, 15 Jan 2005 23:48:33 +0100 Organization: Computel Standby BV MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/166 X-Sequence-Number: 16025 Hi, Sorry for replying to myself, but I had to point out that: >> I'm guessing that the new table/index files created during the CLUSTER >> didn't get released after the PANIC. Look for files that are not >> referenced by any relfilenode value in pg_class. > > Using the oid2name tool I get this: > [...] > I suspect all the files with "No tables with that oid found" can be > removed, but I don't know exactly how oid2name works, so I'll check them > against pg_class before removing them. This is ofcourse not a good idea. There is quite a difference between the oid and the relfilenode. Comparing the output of: SELECT DISTINCT relfilenode FROM pg_class ORDER BY relfilenode; to the directory listing gave a much better result. The files I found in this way also had an atime which was the same as the time of the crash. Just to prevent someone else from making the mistake I made in my previous message... Thanks! Sander.