begin forwarded message:
Date: Thu, 7 Mar 2002 15:32:07 -0500
From: george young <gry@ll.mit.edu>
To: Stephan Szabo <sszabo@megazone23.bigpanda.com>
Subject: Re: [SQL] 7.0.3 pg_dump -> segmentation fault!
On Thu, 7 Mar 2002 12:27:49 -0800 (PST)
Stephan Szabo <sszabo@megazone23.bigpanda.com> 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 isnot 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"
