Re: Blown Index? Corrupted Table?

From: Adam Haberlach <adam(at)newsnipple(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Blown Index? Corrupted Table?
Date: 2000-10-06 19:46:20
Message-ID: 20001006124619.A32282@ricochet.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Oct 06, 2000 at 12:29:29PM -0700, Adam Haberlach wrote:
> I've been getting this on and off in my vaccums. Once it happens, the only way to
> make it go away seems to be a dump/restore. Is this bad, Bad, or BAD?
>
> NOTICE: Index idx_rawbebugs_assignedto: Pages 112; Tuples 31161: Deleted 0. CPU 0.01s/0.10u sec.
> NOTICE: Rel rawbebugs: Pages: 4435 --> 4400; Tuple(s) moved: 0. CPU 0.04s/0.01u sec.
> NOTICE: FlushRelationBuffers(rawbebugs, 4400): block 287 is referenced (private 0, global 1)
> FATAL 1: VACUUM (vc_repair_frag): FlushRelationBuffers returned -2

Ok. It looks like I have one or more Relations pinned in my cache, according
to the source code. Do I need to kick all of the connections out of the
database in order to vaccum? AFAIK, there isn't anyone accessing at the
time (and I tried shutting down httpd while running the vacuum).

--
Adam Haberlach | A billion hours ago, human life appeared on
adam(at)newsnipple(dot)com | earth. A billion minutes ago, Christianity
http://www.newsnipple.com | emerged. A billion Coca-Colas ago was
'88 EX500 | yesterday morning. -1996 Coca-Cola Ann. Rpt.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message bmccoy 2000-10-06 20:49:26 Re: image storing
Previous Message asbjs 2000-10-06 19:33:44 Errors with pg_dump