Skip site navigation (1) Skip section navigation (2)

Re: BUG #2568: Vacuum locks tables and do nothing

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jaroslav Prodelal" <slavek(at)pearshealthcyber(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2568: Vacuum locks tables and do nothing
Date: 2006-08-09 02:05:43
Message-ID: 14747.1155089143@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Jaroslav Prodelal" <slavek(at)pearshealthcyber(dot)com> writes:
>    When vacuum starts vacuuming problematic table, it locks table and
> although, I can't see any load on the server even on disk, cpu or memory,
> table is lock and other processes can't access it. I have also tried strace
> on VACUUM process, but there wasn't any activity on it.

It sounds to me like vacuum is blocked waiting for some other process's
lock --- and then other processes queue up behind vacuum's request, but
that doesn't make it vacuum's fault.  Try looking in pg_locks to see
which process actually has a granted lock on that table.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: tomasDate: 2006-08-09 05:31:07
Subject: Re: BUG #2565: pg tool doesn't detect window size changes
Previous:From: Tom LaneDate: 2006-08-09 02:03:21
Subject: Re: BUG #2565: pg tool doesn't detect window size changes

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group