From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Patrick Robin <Patrick(dot)Robin(at)disney(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump return failed sanity check |
Date: | 2000-05-18 03:18:54 |
Message-ID: | 21336.958619934@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-sql |
Patrick Robin <Patrick(dot)Robin(at)disney(dot)com> writes:
> When I try to use pg_dump, I get this error. Can it have something to
> do with a custom type I added. I made sure I added the input/output functions
> and comparision functions for sorting and queries.
> The type works fine in SQL queries in general.
>> pg_dump -s scm
> \connect - d23adm
> failed sanity check, type with oid 457690 was not found
That's probably an indication that you forgot to delete a function that
takes or returns an older custom type that you deleted.
Look in pg_proc for a function containing 457690 in proargtypes or
prorettype, and delete that tuple (or tuples if more than one).
pg_dump oughta be more helpful about where it sees the problem...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Karl DeBisschop | 2000-05-18 05:37:53 | Re: getting libperl.so |
Previous Message | Bruce Momjian | 2000-05-18 02:28:39 | Re: initdb and "exit_nicely"... |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-05-18 03:26:30 | Re: AW: type conversion discussion |
Previous Message | Tom Lane | 2000-05-18 02:35:33 | Re: question about index cost estimates |
From | Date | Subject | |
---|---|---|---|
Next Message | Gerhard Dieringer | 2000-05-18 06:52:32 | Antw: Automatic index numbers |
Previous Message | Tom Lane | 2000-05-18 02:52:35 | Re: Using substr with user defined types |