RE: Vacuum/mdtruncate() (was: RE: [HACKERS] Current TODO list)

> -----Original Message-----
> From: root(at)sunpine(dot)krs(dot)ru [mailto:root(at)sunpine(dot)krs(dot)ru]On Behalf Of Vadim
> Mikheev
> Sent: Monday, May 24, 1999 4:53 PM
> To: Ole Gjerde
> Cc: Hiroshi Inoue; Bruce Momjian; PostgreSQL-development
> Subject: Re: Vacuum/mdtruncate() (was: RE: [HACKERS] Current TODO list)
>
>
> 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

Are delete/vacuums executed sequentially by single session ?

> > 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?
>

I couldn't reproduce NOT THE SAME message in current.

Thanks.

Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp