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@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83


Mon, 5 Oct 1998 05:05:34 +0300 (MSK)
Oleg Bartunov <oleg@sai.msu.su>
vacuum analyze problem
> 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. 

Just tested on BSDI, and I can't reproduce the problem here.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026


Sun, 4 Oct 1998 22:54:14 -0400 (EDT)
Bruce Momjian <maillist@candle.pha.pa.us>
Re: [HACKERS] vacuum analyze problem
> 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
*snip*
> 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.

I'm not seeing this problem on my Linux machine (2.0.30 kernel) so it
probably isn't a general problem with Linux. I haven't done a completely
new refresh of my sources for at least a few days, though I don't think
this is the problem because you've been seeing something like this on
your machine for a while.

Your problem would be easier to diagnose if someone could reproduce it
on another machine, but if the test is as simple as trying a vacuum on
the regression database then it's easy to test and we aren't finding it
happening everywhere :(

Keep plugging away at it though because there's always a chance that
your particular machine is uncovering an obscure feature of the code...

                    - Tom

Mon, 05 Oct 1998 03:28:31 +0000
"Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Re: [HACKERS] vacuum analyze problem