Skip site navigation (1) Skip section navigation (2)

Re: Re: Vaccuum Failure w/7.1beta4 on Linux/Sparc -- FALSE ALARM

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ryan Kirkpatrick <pgsql(at)rkirkpat(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: Vaccuum Failure w/7.1beta4 on Linux/Sparc -- FALSE ALARM
Date: 2001-03-26 05:16:35
Message-ID: 22271.985583795@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Ryan Kirkpatrick <pgsql(at)rkirkpat(dot)net> writes:
> On Mon, 12 Mar 2001, Ryan Kirkpatrick wrote:
>> While testing some existing database applications on 7.1beta4 on
>> my Sparc 20 running Debian GNU/Linux 2.2, I got the following error on
>> attempting to do a vacuum of a table:
>> 
>> NOTICE:  FlushRelationBuffers(jobs, 1399): block 953 is referenced (private 0, global 1)
>> ERROR! Can't vacuum table Jobs! ERROR:  VACUUM (repair_frag): FlushRelationBuffers returned -2

This is probably explained by the problem we found a few days ago with
BufferSync acquiring locks it shouldn't.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-03-26 05:40:04
Subject: Re: Random make check failures
Previous:From: Rainer MagerDate: 2001-03-26 04:46:43
Subject: Dead locks

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group