Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (Postfix) with ESMTP id 4D6CB4758E3 for ; Thu, 7 Mar 2002 15:27:49 -0500 (EST) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 0BF6AD602; Thu, 7 Mar 2002 12:27:50 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id F199F5BFC; Thu, 7 Mar 2002 12:27:49 -0800 (PST) Date: Thu, 7 Mar 2002 12:27:49 -0800 (PST) From: Stephan Szabo To: george young Cc: Subject: Re: 7.0.3 pg_dump -> segmentation fault! In-Reply-To: <20020307151753.720c9756.gry@ll.mit.edu> Message-ID: <20020307122616.B87178-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200203/88 X-Sequence-Number: 6969 On Thu, 7 Mar 2002, george young wrote: > In fact there is no row in pg_proc with oid=1132416. > > select * from pg_trigger; > tgrelid | tgname | tgfoid | tgtype | tgenabled | tgisconstraint | tgconstrname | tgconstrrelid | tgdeferrable | tginitdeferred | tgnargs | tgattr | tgargs > ---------+----------------+---------+--------+-----------+----------------+--------------+---------------+--------------+----------------+---------+--------+-------- > 1260 | pg_sync_pg_pwd | 12 | 29 | t | f | | 0 | f | f | 0 | | > 1131188 | run_changed_tr | 1132416 | 17 | t | f | | 0 | f | f | 0 | | > (2 rows) > > I'm hoping there is some safe way to manually delete the inconsistant rows and then pg_dump. > Does anyone have a suggestion how to recover from this situation? Can you just do a DROP TRIGGER run_changed_tr ON runs_tmp; and get rid of it?