Re: sanity check error for pg_dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: PRAGATI SAVAIKAR <pragati(at)phil(dot)com(dot)sg>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: sanity check error for pg_dump
Date: 2001-04-06 05:44:02
Message-ID: 23059.986535842@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PRAGATI SAVAIKAR <pragati(at)phil(dot)com(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2001-04-06 05:58:48 Re: Unexpected query results
Previous Message Darren King 2001-04-05 16:00:21 RE: compilation error