| From: | Vadim Mikheev <vadim(at)krs(dot)ru> |
|---|---|
| To: | Ole Gjerde <gjerde(at)icebox(dot)org> |
| Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Vacuum/mdtruncate() (was: RE: [HACKERS] Current TODO list) |
| Date: | 1999-05-24 07:52:55 |
| Message-ID: | 37490557.3B11EC8C@krs.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 1999-05-24 09:50:55 | RE: Vacuum/mdtruncate() (was: RE: [HACKERS] Current TODO list) |
| Previous Message | Ole Gjerde | 1999-05-24 06:48:07 | Re: [HACKERS] Sequence nexvtal() and initdb/pg_proc problem |