Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by postgresql.org (Postfix) with ESMTP id F0FC0476237
	for <pgsql-admin@postgresql.org>; Mon, 25 Feb 2002 18:12:44 -0500 (EST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g1PNCkS25180;
	Mon, 25 Feb 2002 18:12:46 -0500 (EST)
To: s.chava@wcom.com (Srinivasa Rao Chava)
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_dump error 
In-reply-to: <66d229f1.0202251332.3e79fa16@posting.google.com> 
References: <66d229f1.0202251332.3e79fa16@posting.google.com>
Comments: In-reply-to s.chava@wcom.com (Srinivasa Rao Chava)
	message dated "25 Feb 2002 13:32:43 -0800"
Date: Mon, 25 Feb 2002 18:12:46 -0500
Message-ID: <25177.1014678766@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200202/344
X-Sequence-Number: 3497

s.chava@wcom.com (Srinivasa Rao Chava) writes:
> pg_dump: query to obtain procedure name for trigger
> "ins_extranet_cspm_bug" did not return exactly one result

The most likely bet is that there's no function at all that matches the
OID stored in the trigger.  Have you done any deletion/recreation of
functions in the new database?

The error message that 7.2's pg_dump emits here seems less helpful than
the old one :-(.  Will see if I can tweak it.

			regards, tom lane