Re: sanity error with pg_dump on postgresql 7.0.2 - Mailing list pgsql-admin

From Tom Lane
Subject Re: sanity error with pg_dump on postgresql 7.0.2
Date
Msg-id 13326.1041953356@sss.pgh.pa.us
Whole thread Raw
In response to sanity error with pg_dump on postgresql 7.0.2  ("Dan Langille" <dan@langille.org>)
Responses Re: sanity error with pg_dump on postgresql 7.0.2  ("Dan Langille" <dan@langille.org>)
List pgsql-admin
"Dan Langille" <dan@langille.org> writes:
> I am forwarding this on behalf of bain@tcsn.co.za who is at a client
> site and cannot email.

> I did a search and found a mail stating that its possibly related to
> a deleted user having ownership of the table.
> "http://www.geocrawler.com/mail/msg.php3?msg_id=5653159&list=10" I
> checked and indeed the owner that created the table no longer exists.
> Unfortunately I have no idea who that user was.

You don't need to know.  Get the old owner's sysid with
    SELECT relowner FROM pg_class WHERE relname = 'busted_table';
then create a user with the appropriate sysid:
    CREATE USER foo WITH SYSID nnn;

Once you've done that, consider upgrading to a more recent Postgres.
It's been a good long while since pg_dump would choke on this situation.

            regards, tom lane

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Vacuum explained -> Dangerous ?
Next
From: "Gareth Kirwan"
Date:
Subject: Postgresql 7.3 and startup