Hello.

Recently some users started to complain about:
Warning: PostgresSQL query failed: FATAL 1: btree: lost page in the chain of duplicates

I  noticed  that  VACUUM removes this problem, but no making
VACUUM I've got:
NOTICE:  BlowawayRelationBuffers(confread, 45): block 154 is referenced (private 0, last 0,
global 1)
FATAL 1:  VACUUM (vc_rpfheap): BlowawayRelationBuffers returned -2

What it can be? I'm using 6.3.2

Andrey



Tue, 2 Feb 1999 15:15:20 +0300
������������������ ��������������������� <novikov@webclub.ru>
VACUUM problem
On Tue, 2 Feb 1999, XXXXXX XXXXXXX wrote:

> Hello.
> 
> Recently some users started to complain about:
> Warning: PostgresSQL query failed: FATAL 1: btree: lost page in the chain of duplicates
> 
> I  noticed  that  VACUUM removes this problem, but no making
> VACUUM I've got:
> NOTICE:  BlowawayRelationBuffers(confread, 45): block 154 is referenced (private 0, last 0,
> global 1)
> FATAL 1:  VACUUM (vc_rpfheap): BlowawayRelationBuffers returned -2
> 
> What it can be? I'm using 6.3.2

	A relatively old version of PostgreSQL...upgrade to v6.4.2, as I
believe this was fixed several months ago, in v6.4...

Marc G. Fournier                                
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 


Tue, 2 Feb 1999 08:38:51 -0400 (AST)
The Hermit Hacker <scrappy@hub.org>
Re: [HACKERS] VACUUM problem