Re: Error while dropping a table - Mailing list pgsql-general

From Johnson, Shaunn
Subject Re: Error while dropping a table
Date
Msg-id 73309C2FDD95D11192E60008C7B1D5BB04C73D22@snt452.corp.bcbsm.com
Whole thread Raw
In response to Error while dropping a table  ("Johnson, Shaunn" <SJohnson6@bcbsm.com>)
Responses Re: Error while dropping a table  (Andrew Sullivan <andrew@libertyrms.info>)
List pgsql-general

Thanks for the reply:

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]

[snip rest of email]

--Okay, but now, how do I find out what client is holding
--the table hostage?  Generally, I would do something like
--'pg_query' and see what people are doing and against
--whatever table ... but it doesn't appear to be the case
--in this matter.

--Any particular method in finding this out?

This suggests that you've got some other backend that's been sitting
in an open transaction for a long time.  While that isn't directly
harmful, it'll probably be blocking VACUUM, so you might want to
figure out which client is holding the open transaction and zap it.

                        regards, tom lane

--Thanks again!

-X

pgsql-general by date:

Previous
From: vitorgv@lncc.br
Date:
Subject: pg_group and pg_user
Next
From: Andrew Sullivan
Date:
Subject: Re: Migrating database (7.1.3 - 7.2.1)