New fail in vacuum?

Greetings again Tom and pgsql-general users,

I found another error. This time is when I execute vacuumdb. Why vacuum
stops at this point? Should it just create indexes and keep executing?

NOTICE:  --Relation oper_juntor--
NOTICE:  Pages 238: Changed 1, reaped 236, Empty 0, New 0; Tup 570: Vac
36739, Keep/VTL 0/0, Crash 0, UnUsed 45, MinLen 48, MaxLen 48; Re-u
sing: Free/Avail. Space 1770976/1768172; EndEmpty/Avail. Pages 0/235. CPU
0.05s/0.04u sec.
NOTICE:  Index xpkoper_juntor: Pages 198; Tuples 582: Deleted 247. CPU
0.07s/0.01u sec.
NOTICE:  Index xpkoper_juntor: NUMBER OF INDEX' TUPLES (582) IS NOT THE SAME
AS HEAP' (570).
        Recreate the index.
<<vilson : execution stops here>>

Regards,
José Vilson de Mello de Farias
Dígitro Tecnologia Ltda - Brasil

----- Original Message -----
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Vilson farias <vilson.farias@digitro.com.br>
Cc: <pgsql-general@postgresql.org>; SIMONE Carla MOSENA
<simone.mosena@digitro.com.br>
Sent: Quinta-feira, 15 de Março de 2001 18:08
Subject: Re: [GENERAL] Why my vacuum fails?


: "Vilson farias" <vilson.farias@digitro.com.br> writes:
: >   The main problems appears to be related with "Cannot insert a
duplicate
: > key into unique index pg_attribute_relid_attnum_index" message. How can
I
: > fix it?
:
: What platform are you running on, and how did you build or acquire the
: executables?  Have you ever run the regression tests?
:
: This looks a lot like known portability problems on PPC, Alpha, etc.
: There are workarounds but you need to know about them when building...
:
: regards, tom lane
: