Did you not mention that this server was a slony slave at some point though?
Just because you have removed slony, and the error comes from postgresql itself does not mean the corruption was not
causedby misuse of slony.
--- On Wed, 12/5/10, Grzegorz Jaśkiewicz <gryzman@gmail.com> wrote:
> From: Grzegorz Jaśkiewicz <gryzman@gmail.com>
> Subject: Re: [GENERAL] 8.3.7, 'cache lookup failed' for a table
> To: "Alban Hertroys" <dalroi@solfertje.student.utwente.nl>
> Cc: pgsql-general@postgresql.org
> Date: Wednesday, 12 May, 2010, 10:57
> no it is not slony related.
> It is a postgresql problem.
>
> my original post:
> http://archives.postgresql.org/pgsql-general/2010-05/msg00402.php
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
