Re: vacuum error "left link changed unexpectedly"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ulrich Wisser <ulrich(dot)wisser(at)relevanttraffic(dot)se>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: vacuum error "left link changed unexpectedly"
Date: 2005-08-15 13:28:34
Message-ID: 25168.1124112514@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ulrich Wisser <ulrich(dot)wisser(at)relevanttraffic(dot)se> writes:
> INFO: vacuuming "public.userclick"
> INFO: index "userclick_i01" now contains 13715747 row versions in 60640
> pages
> DETAIL: 0 index row versions were removed.
> 14209 index pages have been deleted, 14209 are currently reusable.
> CPU 2.46s/6.06u sec elapsed 186.45 sec.
> ERROR: left link changed unexpectedly

> To me this looks as the index userclick_i01 is corrupted.

No, it would be the one next to be processed. VACUUM does them in OID
order, so try something like

select indexrelid::regclass from pg_index
where indrelid = 'public.userclick'::regclass
order by indexrelid;

and look to see which index comes after userclick_i01.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-08-15 13:37:27 Re: hash-join forgets tuples
Previous Message Richard Sydney-Smith 2005-08-15 12:58:52 Authenticating using Windows XP login