Received: from ll.mit.edu (LLMAIL.LL.MIT.EDU [129.55.12.40]) by postgresql.org (Postfix) with ESMTP id CDCF6476055 for ; Thu, 7 Mar 2002 15:44:36 -0500 (EST) Received: (from smtp@localhost) by ll.mit.edu (8.11.3/8.8.8) id g27Kibm04673 for ; Thu, 7 Mar 2002 15:44:37 -0500 (EST) Received: from UNKNOWN( ), claiming to be "sty" via SMTP by llmail, id smtpdAAA3oaW0i; Thu Mar 7 15:44:32 2002 Date: Thu, 7 Mar 2002 15:44:31 -0500 From: george young To: pgsql-sql@postgresql.org Subject: Fw: Re: 7.0.3 pg_dump -> segmentation fault! Message-Id: <20020307154431.769de3d8.gry@ll.mit.edu> Reply-To: gry@ll.mit.edu Organization: MIT Lincoln Laboratory X-Mailer: Sylpheed version 0.7.0 (GTK+ 1.2.8; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200203/91 X-Sequence-Number: 6972 begin forwarded message: Date: Thu, 7 Mar 2002 15:32:07 -0500 From: george young To: Stephan Szabo Subject: Re: [SQL] 7.0.3 pg_dump -> segmentation fault! On Thu, 7 Mar 2002 12:27:49 -0800 (PST) Stephan Szabo wrote: > 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? Alas, no. I get: drop trigger run_chaged_tr on runs_tmp; ERROR: RelationBuildTriggers: tgargs IS NULL for rel runs_tmp In fact, anything I try to do to runs_tmp I get the same above error, select, delete, drop... This table is not important and if I could blow it and the trigger away, that would be great. -- I cannot think why the whole bed of the ocean is not one solid mass of oysters, so prolific they seem. Ah, I am wandering! Strange how the brain controls the brain! -- Sherlock Holmes in "The Dying Detective"