Skip site navigation (1) Skip section navigation (2)

Rare corruption of pg_class index

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Rare corruption of pg_class index
Date: 2006-12-20 18:06:29
Message-ID: 5df4b0d9bb27de3fb6e606e661e2e5db@biglumber.com (view raw or flat)
Thread:
Lists: pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I'm encountering some disconcerting problems on a 8.1.3 database.
Very occasionally, I get a "could not open relation with OID xxx".
This always occurs inside of a plpgsql function, and always refers
to a normal, stable table that has not been dropped. The first
time this occured, I reindexed the system indexes, but it has occured
again, and on more than one database, which seems to lessen the chance
of a hardware issue or a temporary index corruption issue. The functions
in question are called many times, but the error only happens once in
a blue moon. The last time it happened, the function ran with no problem
one minute before the error, and again four minutes afterwards. The
table name is hard-coded into the functions. This happens on average
five times a day or so, on a very busy database (> 10M statements/day,
the functions fire tens of thousands of times)

Any clues on what could be causing this, or ways to go forward on
debugging? Thanks.

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200612201252
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFFiXmzvJuQZxSWSsgRAkr4AKDhTKTILjrVbitWTu4wzktejXD2egCfSk/H
h+vBn6lJegKeRD+tsBFSYng=
=svv7
-----END PGP SIGNATURE-----



Responses

pgsql-hackers by date

Next:From: Jeff DavisDate: 2006-12-20 18:21:57
Subject: Re: Rare corruption of pg_class index
Previous:From: Teodor SigaevDate: 2006-12-20 17:35:56
Subject: tsearch in core patch, for review

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group