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

vacuum analyze problem

From: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
To: hackers(at)postgreSQL(dot)org
Subject: vacuum analyze problem
Date: 1998-10-05 02:05:34
Message-ID: Pine.GSO.3.96.SK.981005050017.3285A-100000@ra (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi,

cvs still has problem with vacuum analyze on my Linux machine:
after completion of regression test which passed fine I tried
vacuum analyze on regression db and got 

NOTICE:  AbortTransaction and not in in-progress state 
NOTICE:  AbortTransaction and not in in-progress state 

in regress.log there were following messages:
......skipped....
ages 0/0. Elapsed 0/0 sec.
DEBUG:  --Relation lseg_tbl--
DEBUG:  Pages 1: Changed 0, Reapped 0, Empty 0, New 0; Tup 5: Vac 0, Crash 0, UnUsed 0, MinLen 72, MaxLen 72; Re-using: Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
ERROR:  cannot write block 0 of pkeys [regression] blind
NOTICE:  AbortTransaction and not in in-progress state 
ERROR:  cannot write block 0 of pkeys [regression] blind
NOTICE:  AbortTransaction and not in in-progress state 
ERROR:  cannot write block 0 of pkeys [regression] blind
NOTICE:  AbortTransaction and not in in-progress state 

Earlier this happened only if I run postmaster with number of buffers > 128
and never happens when I run regression test following procedure
described in INSTALL. 

	Oleg



_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83


Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 1998-10-05 02:54:14
Subject: Re: [HACKERS] vacuum analyze problem
Previous:From: Tatsuo IshiiDate: 1998-10-05 02:04:12
Subject: Re: [HACKERS] Open 6.4 items

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