Re: Vacuum/mdtruncate() (was: RE: [HACKERS] Current TODO list) - Mailing list pgsql-hackers

From Vadim Mikheev
Subject Re: Vacuum/mdtruncate() (was: RE: [HACKERS] Current TODO list)
Date
Msg-id 37490557.3B11EC8C@krs.ru
Whole thread Raw
In response to Vacuum/mdtruncate() (was: RE: [HACKERS] Current TODO list)  (Ole Gjerde <gjerde@icebox.org>)
Responses RE: Vacuum/mdtruncate() (was: RE: [HACKERS] Current TODO list)  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
List pgsql-hackers
Ole Gjerde wrote:
> 
> While doing a bunch of vacuums, I have seen some strange things(so my
> patch probably isn't 100%).
> I started with 58 segments, and did a bunch of delete/vacuums and got it
> down to about 5-6.  Then I got the error below while running a vacuum
> analyze.  This appeared after the index clean, but before any tuples were
> moved.
> ERROR:  HEAP_MOVED_IN was not expected

I added this in my last patch ... I have to think more about
the cause.

> Also, I was seeing some more errors about INDEX' TUPLES being higher than
> HEAP TUPLES.  Didn't this just get fixed, or did I break something with my
> patch.  I was seeing these after doing delete/vacuums with my patch.

Hiroshi, could you try to reproduce NOT THE SAME problem
with new vacuum code?

Vadim


pgsql-hackers by date:

Previous
From: Ole Gjerde
Date:
Subject: Re: [HACKERS] Sequence nexvtal() and initdb/pg_proc problem
Next
From: "Hiroshi Inoue"
Date:
Subject: RE: Vacuum/mdtruncate() (was: RE: [HACKERS] Current TODO list)