Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id XAA22875 for ; Wed, 17 May 2000 23:18:58 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id XAA21339; Wed, 17 May 2000 23:18:55 -0400 (EDT) To: Patrick Robin cc: pgsql-general@postgresql.org Subject: Re: pg_dump return failed sanity check In-reply-to: <3922D330.470E9451@fa.disney.com> References: <14625.26748.356187.68826@localhost.grauel.com> <39223072.63596770@alumni.caltech.edu> <14626.41891.173479.250021@localhost.grauel.com> <17483.958581314@sss.pgh.pa.us> <3922D330.470E9451@fa.disney.com> Comments: In-reply-to Patrick Robin message dated "Wed, 17 May 2000 10:13:20 -0700" Date: Wed, 17 May 2000 23:18:54 -0400 Message-ID: <21336.958619934@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200005/95 Patrick Robin 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