From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Lohse <al@humantouch.de>
Cc: pgsql-admin@postgresql.org
Subject: Re: Problems with missing OIDs
Date: Sat, 03 Nov 2007 13:00:49 -0400
Message-ID: <11596.1194109249@sss.pgh.pa.us> (raw)
In-Reply-To: <043A7BA3-8C72-4D9C-B7DD-52B183A2B313@humantouch.de>
References: <043A7BA3-8C72-4D9C-B7DD-52B183A2B313@humantouch.de>
Alexander Lohse <al@humantouch.de> writes:
> after a disk-crash some weeks ago and a successful recovery, I now
> find some strange issues in postgres.
> I am not sure they are related to the crash, but I figure chances
> are ...
That really shouldn't have happened in the first place. Are you running
an up-to-date Postgres version? Are you sure your disk drives don't lie
about write completion?
> One of them is: When trying to vacuum one database I get the following
> message:
> "ERROR: could not open relation with OID 36893600"
> Now I searched and found a row in pg_index with
> indexrelid => 36893600
> Is it save to just drop this row? Or how do I find out which index is
> affected?
Well, if the pg_class row with that OID is gone, then there's no direct
way to know. But you should be able to look at the row referenced by
indrelid, to find out which table it was an index *of*. Hopefully you
know your schema well enough to figure out which of its indexes is
missing.
I would recommend a dump/initdb/reload cycle to try to detect and clean
up any other corruption. Loss of just one pg_class row doesn't seem
like a very probable failure, so I'm afraid you may have more problems.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, al@humantouch.de
Subject: Re: Problems with missing OIDs
In-Reply-To: <11596.1194109249@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox