| From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
|---|---|
| To: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: autovac hung/blocked |
| Date: | 2006-11-14 19:53:56 |
| Message-ID: | 200611141253.56301.pgsql@bluepolka.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tuesday November 14 2006 12:49 pm, Jim C. Nasby wrote:
> On Tue, Nov 14, 2006 at 11:20:30AM -0700, Ed L. wrote:
> > I have an 8.1.2 autovac which appears to be hanging/blocking
> > every few days or so, but we're don't understand what's
> > causing it. I wasn't able to catch a backtrace before we
> > killed it. I do not see autovac locks in the pg_locks view.
> >
> > Will running 8.1.5 buy me anything in terms of being able to
> > see what it has locked and what locks it might be awaiting?
> > Or maybe in terms of bugs that might explain it?
>
> If there's no locks, why do you think it's blocked?
I had wondered if all autovac locks were in the pg_locks view,
but I now see them. A gdb backtrace a few days ago had autovac
waiting on a semaphore, and I assumed that was waiting on a
lock.
Ed
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-11-14 19:56:18 | Re: autovac hung/blocked |
| Previous Message | Jim C. Nasby | 2006-11-14 19:51:26 | Re: FW: [NOVICE] Creating a new server |