Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 770142E0031 for ; Tue, 10 Jun 2008 14:09:23 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 69174-10 for ; Tue, 10 Jun 2008 14:09:19 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by developer.postgresql.org (Postfix) with ESMTP id 314212E002E for ; Tue, 10 Jun 2008 14:09:17 -0300 (ADT) Received: from perhan.alvh.no-ip.org (190-95-18-208.bk17-dsl.surnet.cl [190.95.18.208]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m5AHAnWh014432 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Jun 2008 10:10:52 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 2CAC047C7C; Tue, 10 Jun 2008 13:09:11 -0400 (CLT) Date: Tue, 10 Jun 2008 13:09:11 -0400 From: Alvaro Herrera To: Hays Steve - sthays Cc: pgsql-admin@postgresql.org Subject: Re: Cannot Drop Schema Message-ID: <20080610170911.GI5198@alvh.no-ip.org> References: <862C6118C84D1C43AE2146394535830607A1A293@CWYMSX06.Corp.Acxiom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <862C6118C84D1C43AE2146394535830607A1A293@CWYMSX06.Corp.Acxiom.net> User-Agent: Mutt/1.5.18 (2008-05-17) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Tue, 10 Jun 2008 10:10:52 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/77 X-Sequence-Number: 29415 Hays Steve - sthays wrote: > There is a schema we created and has been in use for several months that > now seems to have some objects that cannot be dropped. When I attempt to > drop a suspect table in this schema, the process just runs, as though it > is being blocked by an active DML process, but this is even after a > server restart. Maybe you have prepared transactions. Look in the pg_prepared_xacts view, and issue ROLLBACK PREPARED or COMMIT PREPARED if so. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support