Re: 7.0.3 pg_dump -> segmentation fault!

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?