Re: [HACKERS] vacuum analyze problem

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: oleg(at)sai(dot)msu(dot)su (Oleg Bartunov)
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] vacuum analyze problem
Date: 1998-10-05 02:54:14
Message-ID: 199810050254.WAA02131@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
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.

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

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas G. Lockhart 1998-10-05 03:15:34 Re: pg_dump new -n flag
Previous Message Oleg Bartunov 1998-10-05 02:05:34 vacuum analyze problem