Re: [HACKERS] vacuum analyze problem - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] vacuum analyze problem
Date
Msg-id 199810050254.WAA02131@candle.pha.pa.us
Whole thread Raw
In response to vacuum analyze problem  (Oleg Bartunov <oleg@sai.msu.su>)
List 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.

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


pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: vacuum analyze problem
Next
From: "Thomas G. Lockhart"
Date:
Subject: Re: pg_dump new -n flag