Re: sanity check error for pg_dump - Mailing list pgsql-bugs

From Tom Lane
Subject Re: sanity check error for pg_dump
Date
Msg-id 23059.986535842@sss.pgh.pa.us
Whole thread Raw
In response to sanity check error for pg_dump  (PRAGATI SAVAIKAR <pragati@phil.com.sg>)
List pgsql-bugs
PRAGATI SAVAIKAR <pragati@phil.com.sg> writes:
> We have recently started getting following error messages
> failed sanity check, table arind was not found
> failed sanity check, table inpart was not found
>  due to which pg_dump  process does not get complete.

It's a good bet that these tables belong to a user who's been dropped
from pg_shadow.  Check their pg_class entries to see what the relowner
field is.  You can either create a new user entry with a matching
usesysid value, or change the relowner fields to match an existing user.

            regards, tom lane

pgsql-bugs by date:

Previous
From: PRAGATI SAVAIKAR
Date:
Subject: sanity check error for pg_dump
Next
From: Tom Lane
Date:
Subject: Re: Unexpected query results