Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2] (may be
	forged)) by hub.org (8.9.3/8.9.3) with ESMTP id UAA09248
	for <pgsql-interfaces@postgreSQL.org>;
	Thu, 22 Jul 1999 20:55:13 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id UAA11162;
	Thu, 22 Jul 1999 20:54:05 -0400 (EDT)
To: Zakkr <zakkr@zf.jcu.cz>
cc: pgsql-interfaces <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] SPI_exec vs. CREATE/DROP RULE 
In-reply-to: Your message of Thu, 22 Jul 1999 13:01:54 +0200 (CEST)
	<Pine.LNX.3.96.990722125322.459A-100000@ara.zf.jcu.cz>
Date: Thu, 22 Jul 1999 20:54:05 -0400
Message-ID: <11160.932691245@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Zakkr <zakkr@zf.jcu.cz> writes:
> I try in my function use SPI_exec() with CREATE or DROP RULE, but if I call
> my func. - server return this message: 
> "Backend send D message without prior T". 

That's a known bug with utility statements executed via SPI.  Someone
was looking into a fix a few months ago, but I haven't heard anything
about it since then...

			regards, tom lane