Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Lock issue when trying to vacuum db
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Jess Balint" <jbalint(at)gmail(dot)com>
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: Lock issue when trying to vacuum db
- Date: Mon, 19 Dec 2005 22:03:29 -0500
- Message-id: <24291(dot)1135047809(at)sss(dot)pgh(dot)pa(dot)us>
"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
- Follow-Ups:
- Re: Lock issue when trying to vacuum db
- From: Jess Balint
- Re: Lock issue when trying to vacuum db
- References:
- Lock issue when trying to vacuum db
- From: Jess Balint
- Lock issue when trying to vacuum db
- Prev by Date: Re: [pgadmin-hackers] Client-side password encryption
- Next by Date: localization problem (and solution)
- Previous by thread: Lock issue when trying to vacuum db
- Next by thread: Re: Lock issue when trying to vacuum db
- Indexes: