Mike Mascari <[EMAIL PROTECTED]> writes:
> Is there any possibility that he's got an open transacation sitting out
> there for days holding a lock on that table?
Good thought ... but if that was the issue then the DROP would just be
sleeping waiting for the lock, and Eric did say it was consuming
Tom Lane wrote:
"Eric Freeman" <[EMAIL PROTECTED]> writes:
I started the drop table command yesterday and it's been running for almost
24 hours.
You're stuck in some kind of infinite loop --- there's no way that DROP
should take any noticeable amount of time. I'm guessing that the system
"Eric Freeman" <[EMAIL PROTECTED]> writes:
> I started the drop table command yesterday and it's been running for almost
> 24 hours.
You're stuck in some kind of infinite loop --- there's no way that DROP
should take any noticeable amount of time. I'm guessing that the system
catalog entries for
I'm trying to drop a table and it's taking a very long time. There has been
a lot of modification to the table and it has a lot of old data still being
used as a result of not using the vacuum function enough. I ran an insert
into and it was taking a long time (ran for about 48 hours) so I abort
