Re: Stuck vacuum...

From: Mike Diehl <mdiehl(at)diehlnet(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Stuck vacuum...
Date: 2009-10-10 06:54:47
Message-ID: 200910100054.47664.mdiehl@diehlnet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Friday 09 October 2009 08:22:52 pm Tom Lane wrote:
> Mike Diehl <mdiehl(at)diehlnet(dot)com> writes:
> > I'm doing a routine vacuum on my database and it seems to be getting
> > "stuck."
> >
> > I've got a "servers" table with only a few rows and columns in it and
> > this is what vacuum has to say:
> >
> > # VACUUM ANALYZE VERBOSE servers;
> > INFO: vacuuming "public.servers"
> > INFO: scanned index "servers_id" to remove 19200 row versions
> > DETAIL: CPU 0.02s/0.01u sec elapsed 0.03 sec.
> > INFO: scanned index "servers_name" to remove 19200 row versions
> > DETAIL: CPU 0.03s/0.01u sec elapsed 0.05 sec.
> >
> > The problem is that it's been stalled for several minutes. It's
> > beginning to sound like a hard drive problem. Any other ideas?
>
> Maybe it's waiting for some other session to release a page-level lock.
> Have you got anything else running in the database, and if so what is
> that doing?
>
> regards, tom lane

I restarted Postgres and re-ran the vacuum. All seems OK now. Thank you for
your time. I guess I should have refrained from jumping to conclusions.

--

Take care and have fun,
Mike Diehl.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2009-10-10 07:40:26 Re: Access dynamic NEW.column_name in trigger?
Previous Message Tom Lane 2009-10-10 04:21:08 Re: array_agg performance