Re: Lock issue when trying to vacuum db
- From: "Jess Balint" <jbalint(at)gmail(dot)com>
- To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: Lock issue when trying to vacuum db
- Date: Tue, 20 Dec 2005 00:11:43 -0500
- Message-id: <43a7928f(dot)6322ca7b(dot)0584(dot)730d(at)mx(dot)gmail(dot)com>
That was it. There were two in there. I rolled 'em back and everything is
smooth now. Thanks a lot.
Jess
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Monday, December 19, 2005 10:03 PM
To: Jess Balint
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Lock issue when trying to vacuum db
"Jess Balint" <jbalint(at)gmail(dot)com> writes:
> Hi, I have a database that had a large table in it. I dropped the table,
but
> when I try to full vacuum the db, it just freezes indefinitely. There are
> shared locks held on this that I can't identify. I've tried bouncing this
> instance and ran some queries immediately after starting up.
AFAIK, the only way for a lock to survive a database restart is a
prepared transaction. Are you running 8.1, and if so what does
pg_prepared_xacts show?
regards, tom lane
Home |
Main Index |
Thread Index