> > There is a bug in check_foreign_key of refint.c which is bundled with

bmomjian · bmomjian · commit 3abf496b8eb7 · 1998-10-06T03:12:59.000Z
&gt; &gt; the standard distribution. It occurs when a trigger calling this
&gt; &gt; function recursively fires another trigger which calls the same
&gt; &gt; function. The calling check_foreign_key loses its plan informantion and
&gt; &gt; when it tries to use it the backend closes its channel. You can check it
&gt; &gt; with the sql script I am attaching below.
&gt; &gt; The solution to this is to do a find_plan again before executing it at
&gt; &gt; line 483 of refint.c.
&gt; &gt; Therefore two more lines should be added before line 483:

Anand Surelia
diff --git a/contrib/spi/refint.c b/contrib/spi/refint.c
@@ -480,6 +480,8 @@ check_foreign_key()
 
 		relname = args[0];
 
+		sprintf(ident, "%s$%u", trigger->tgname, rel->rd_id);
+		plan = find_plan(ident, &FPlans, &nFPlans);
 		ret = SPI_execp(plan->splan[r], kvals, NULL, tcount);
 		/* we have no NULLs - so we pass   ^^^^  here */
 
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
@@ -281,13 +281,13 @@ catalogs.
 <variablelist>
 <varlistentry>
 <term>
-rules and views
+rules
 <listitem>
 <para>
 <application>pg_dump</application> 
-does not understand user-defined rules and views and
+does not understand user-defined rules and
 will fail to dump them properly.  (This is due to the fact that
-rules are stored as plans in the catalogs and not textually).
+rules are stored as plans in the catalogs and not textually.)
 
 <varlistentry>
 <term>
