Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id D29029FB844 for ; Wed, 4 Apr 2007 13:37:23 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 33200-04 for ; Wed, 4 Apr 2007 13:37:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from 66-226-76-106.dedicated.abac.net (66-226-76-106.dedicated.abac.net [66.226.76.106]) by postgresql.org (Postfix) with ESMTP id 3C7FC9FB6B2 for ; Wed, 4 Apr 2007 13:37:01 -0300 (ADT) Received: (qmail 10043 invoked by uid 2020); 4 Apr 2007 09:37:00 -0700 Received: from wsip-70-167-125-69.sd.sd.cox.net (HELO ?192.168.0.3?) (70.167.125.69) by 192.168.0.4 with (DHE-RSA-AES256-SHA encrypted) SMTP; 4 Apr 2007 09:36:59 -0700 Message-ID: <4613D5BC.2070607@modgraph-usa.com> Date: Wed, 04 Apr 2007 09:43:40 -0700 From: "Craig A. James" User-Agent: Thunderbird 1.5.0.10 (X11/20070221) MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Can't drop tablespace or user after disk gone References: <9C0858F5-0A48-4AF9-80FF-E4BA14F0F965@ohloh.net> <4613053F.5070401@polimetrix.com> <4613C14A.4020703@commandprompt.com> <4613C54C.4050207@kaltenbrunner.cc> <4613C6F1.3090009@commandprompt.com> <4613CB60.6030505@kaltenbrunner.cc> In-Reply-To: <4613CB60.6030505@kaltenbrunner.cc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.574 tagged_above=0 required=5 tests=AWL=-1.245, BAYES_50=0.001, HELO_DYNAMIC_IPADDR2=3.818 X-Spam-Level: ** X-Archive-Number: 200704/78 X-Sequence-Number: 23955 I had a 'scratch' database for testing, which I deleted, and then disk went out. No problem, no precious data. But now I can't drop the tablespace, or the user who had that as the default tablespace. I thought about removing the tablespace from pg_tablespaces, but it seems wrong to be monkeying with the system tables. I still can't drop the user, and can't drop the tablespace. What's the right way to clear out Postgres when a disk fails and there's no reason to repair the disk? Thanks, Craig