vacuum analyze returns "OID IS INVALID. TUPGONE 1" on pg_language

Started by Warren Vanichukabout 25 years ago3 messagesgeneral
Jump to latest
#1Warren Vanichuk
pyber@street-light.com

*sigh* I will learn to use my mail client soon to change subjects. My
apologies. :(

Original Message :
------------------

Greetings.

I just received the following error attempting to do a vacuum on my
database:

freehost=# vacuum analyze;
NOTICE: Rel pg_language: TID 0/1: OID IS INVALID. TUPGONE 1.
ERROR: Index pg_language_oid_index is not a btree

And I see several errors in the logs regarding invalid function calls. When
I attempt to call any user-defined function I receive :

freehost=# select add_pageview( 1 );
ERROR: Index pg_language_oid_index is not a btree

The only oddity during this time was the postgres process handling the
vacuum shot up to 685MB worth of RAM usage (638 shared) during the vacuum.

This is a Debian 2.2 system running PostgreSQL 7.0.3...

Help? :)

Sincerely, Warren

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Warren Vanichuk (#1)
Re: vacuum analyze returns "OID IS INVALID. TUPGONE 1" on pg_language

Warren Vanichuk <pyber@street-light.com> writes:

freehost=# vacuum analyze;
NOTICE: Rel pg_language: TID 0/1: OID IS INVALID. TUPGONE 1.
ERROR: Index pg_language_oid_index is not a btree

Yeek. Something's pretty hosed with pg_language_oid_index. Try
reindexing it. (The procedure to reindex a system index is a bit
arcane, and I have to admit I've never done it myself, but it's in
the documentation.)

regards, tom lane

#3Warren Vanichuk
pyber@street-light.com
In reply to: Tom Lane (#2)
Re: vacuum analyze returns "OID IS INVALID. TUPGONE 1" on pg_language

freehost=# vacuum analyze;
NOTICE: Rel pg_language: TID 0/1: OID IS INVALID. TUPGONE 1.
ERROR: Index pg_language_oid_index is not a btree

Yeek. Something's pretty hosed with pg_language_oid_index. Try
reindexing it. (The procedure to reindex a system index is a bit
arcane, and I have to admit I've never done it myself, but it's in
the documentation.)

Thank you, I found 'reindex' and followed the instructions and everything
appears to be fairly happy again. :)

Sincerely, Warren