Re: Help: 8.0.3 Vacuum of an empty table never completes ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: James Robinson <jlrobins(at)socialserve(dot)com>
Cc: Hackers Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Help: 8.0.3 Vacuum of an empty table never completes ...
Date: 2005-11-28 16:28:34
Message-ID: 10504.1133195314@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

James Robinson <jlrobins(at)socialserve(dot)com> writes:
> As fate would have it, the vacuumdb frontend and backend which were
> initially afflicted are still in existence:

OK, so pid 19244 isn't blocked on any lmgr lock; else we'd see an entry
with granted = f for it in pg_locks. It could be blocked on a lower
level lock though. Can you attach to that PID with gdb and get a stack
trace? Something like (as postgres user)

gdb /path/to/postgres-executable 19244
gdb> bt
gdb> quit
ok to detach? yes

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mario Weilguni 2005-11-28 16:31:09 Re: Getting different number of results when using hashjoin on/off
Previous Message James Robinson 2005-11-28 16:23:47 Re: Help: 8.0.3 Vacuum of an empty table never completes ...