Just a supplement.
Essentially this isn't a crash bug.
This had been a disastrous bug that causes data loss silently.
(This is known as 'HEAP_MOVED_IN was not expected' bug
but the result could be more serious than I've recognized.)
Please apply the patch if you still have pre-7.0 pg db-s and
yo
> Althoug this happens on old 6.5.3, I would like to know if this has
> been already fixed...
>
> Here is the scenario:
>
> 1) before vacuum, table A has 8850 tuples.
>
> 2) vacuum on table A makes postgres crashed.
>
> 3) it crashes at line 1758:
>
> Assert(num_moved == checked_moved);
