From: Stephan Szabo <sszabo@megazone23.bigpanda.com>
To: george young <gry@ll.mit.edu>
Cc: pgsql-sql@postgresql.org
Subject: Re: 7.0.3 pg_dump -> segmentation fault!
Date: Thu, 7 Mar 2002 12:27:49 -0800 (PST)
Message-ID: <20020307122616.B87178-100000@megazone23.bigpanda.com> (raw)
In-Reply-To: <20020307151753.720c9756.gry@ll.mit.edu>
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?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: sszabo@megazone23.bigpanda.com, gry@ll.mit.edu
Subject: Re: 7.0.3 pg_dump -> segmentation fault!
In-Reply-To: <20020307122616.B87178-100000@megazone23.bigpanda.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox