Re: auto vacuum lock on 8.1beta1

From: Robert Creager <Robert(dot)Creager(at)Sun(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PGHackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: auto vacuum lock on 8.1beta1
Date: 2005-10-13 19:40:36
Message-ID: 20051013134036.00000427@C118181.stortek.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 13 Oct 2005 15:09:58 -0400
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Robert Creager <Robert(dot)Creager(at)Sun(dot)com> writes:
> > Might this be the same problem as the recent thread "database vacuum from
> > cron hanging" where Tom is: "I'm busy volatile-izing all the code in
> > bufmgr.c ... should be able to commit a fix soon."?
>
> Seems reasonably likely, seeing that the original report involved gcc
> 3.3.something IIRC, and you're using 3.3.1. Is this an SMP box? The
> bug could theoretically manifest on a uniprocessor but it seems more
> likely to happen on a multiprocessor.

Yes, it's a dual Xenon box.

>
> Too bad you didn't have it built with --enable-debug; I can't think of
> any very easy way to verify a negative refcount for that buffer without
> gdb support.

I just downloaded last nights snapshot. I'll build with debug and try it out.

Thanks,
Rob

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Creager 2005-10-13 19:40:59 Re: auto vacuum lock on 8.1beta1
Previous Message Thomas Hallgren 2005-10-13 19:39:00 Re: pg_config --pgxs on Win32