Re: Error while dropping a table

From: "Johnson, Shaunn" <SJohnson6(at)bcbsm(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Error while dropping a table
Date: 2002-07-25 18:04:56
Message-ID: 73309C2FDD95D11192E60008C7B1D5BB04C73D22@snt452.corp.bcbsm.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks for the reply:

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Elielson Fontanezi 2002-07-25 18:33:49 little shell script
Previous Message vitorgv 2002-07-25 18:04:37 pg_group and pg_user