Re: PostgreSQL 8.1.0 catalog corruption

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bob Ippolito <bob(at)redivi(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PostgreSQL 8.1.0 catalog corruption
Date: 2005-11-21 21:59:33
Message-ID: 4637.1132610373@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bob Ippolito <bob(at)redivi(dot)com> writes:
> The attributes look like the names of all the columns in the table,
> and reindexing didn't help.

So at this point it seems that the pg_class row disappeared, but there
probably wasn't any actual DROP operation --- you'd think at least some
of those other entries would have been deleted by a DROP.

My next guess is that the pg_class row simply got clobbered somehow,
eg its xmin field got set to something ridiculous. The only way I can
think of to investigate that is to dump out the contents of pg_class
with pg_filedump --- are you game for that? If so, get the right
version of pg_filedump from
http://sources.redhat.com/rhdb/utilities.html
and run it with the -i -f options (usually produces the most helpful
output, in my experience).

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2005-11-21 22:05:07 Re: [COMMITTERS] pgsql: make_restrictinfo() failed to attach the specified
Previous Message Bob Ippolito 2005-11-21 21:54:10 Re: PostgreSQL 8.1.0 catalog corruption