Child itemid in update-chain marked as unused - can't continue repair_frag

Started by V. M.over 24 years ago3 messages
#1V. M.
txian@hotmail.com

lindo=# vacuum analyze;
NOTICE: Index probably_good_banner_myidx1: NUMBER OF INDEX' TUPLES (1) IS
NOT THE SAME AS HEAP' (4).
Recreate the index.
NOTICE: Index probably_good_banner_myidx1: NUMBER OF INDEX' TUPLES (1) IS
NOT THE SAME AS HEAP' (4).
Recreate the index.
NOTICE: Child itemid in update-chain marked as unused - can't continue
repair_frag
VACUUM

what i must do here?

thanks,
valter
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

#2Bruce Momjian
pgman@candle.pha.pa.us
In reply to: V. M. (#1)
Re: Child itemid in update-chain marked as unused - can't continue repair_frag

lindo=# vacuum analyze;
NOTICE: Index probably_good_banner_myidx1: NUMBER OF INDEX' TUPLES (1) IS
NOT THE SAME AS HEAP' (4).
Recreate the index.
NOTICE: Index probably_good_banner_myidx1: NUMBER OF INDEX' TUPLES (1) IS
NOT THE SAME AS HEAP' (4).
Recreate the index.
NOTICE: Child itemid in update-chain marked as unused - can't continue
repair_frag
VACUUM

I would drop and recreate the index.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: V. M. (#1)
Re: Child itemid in update-chain marked as unused - can't continue repair_frag

"V. M." <txian@hotmail.com> writes:

lindo=# vacuum analyze;
NOTICE: Index probably_good_banner_myidx1: NUMBER OF INDEX' TUPLES (1) IS
NOT THE SAME AS HEAP' (4).
Recreate the index.
NOTICE: Index probably_good_banner_myidx1: NUMBER OF INDEX' TUPLES (1) IS
NOT THE SAME AS HEAP' (4).
Recreate the index.
NOTICE: Child itemid in update-chain marked as unused - can't continue
repair_frag
VACUUM

Interesting --- can you show us the sequence that got you into this
state? A reproducible case that causes these messages would be very
useful for debugging.

what i must do here?

Dumping and reloading the table should fix it, if nothing else does.

BTW, what Postgres version is this?

regards, tom lane