Ulrich Wisser <[EMAIL PROTECTED]> writes:
>indexrelid
> ---
> userclick_i01
> userclick_i02
> userclick_i03
> userclick_i04
> userclick_i05
> userclick_i06
> userclick_i07
> (7 rows)
OK, so userclick_i02 appears to be the broken index.
> How do I proceed? How can I t
Hi Tom,
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;
indexrelid
---
userclick_i01
usercli
Ulrich Wisser <[EMAIL PROTECTED]> 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 se
Hi Tom,
I did run vacuum verbose".
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.
Hello Tom,
thanks for your fast answer. And yes it is reproducible. It started
during my vacation (of course!!!) and I get the message ever since
(approx. 6 weeks, vacuum daily).
We use
Fedora Linux Core 2
PostgreSQL 7.4.2
I'll try to get the information you asked for over the weekend.
Ulr
Ulrich Wisser <[EMAIL PROTECTED]> writes:
> vacuumdb: vacuuming of database "CLIX2" failed: ERROR: left link
> changed unexpectedly
Hm, is this repeatable? When I wrote the code I thought it was
a can't-happen case, which is why the error message is so terse
(it was only pure paranoia that made
Hello,
after months of flawless operations suddenly an error occurred.
The database is vacuumed every night. Beside the vacuum error message
the database works fine.
Here the vacuum output:
vacuumdb: vacuuming database "CLIX2"
vacuumdb: vacuuming of database "CLIX2" failed: ERROR: left link
