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: | 2005-12-20 05:11:43 |
Message-ID: | 43a7928f.6322ca7b.0584.730d@mx.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Manuel Sugawara | 2005-12-20 05:24:42 | Re: localization problem (and solution) |
Previous Message | Premsun Choltanwanich | 2005-12-20 04:35:29 | Re: lo function changed in PostgreSQL 8.1.1 |