Skip site navigation (1) Skip section navigation (2)

RE: [INTERFACES] SPI_exec vs. CREATE/DROP RULE

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Zakkr" <zakkr(at)zf(dot)jcu(dot)cz>
Cc: "pgsql-interfaces" <pgsql-interfaces(at)postgreSQL(dot)org>
Subject: RE: [INTERFACES] SPI_exec vs. CREATE/DROP RULE
Date: 1999-07-23 03:05:49
Message-ID: 000601bed4b8$44575e40$2801007e@cadzone.tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-interfaces

> -----Original Message-----
> From: owner-pgsql-interfaces(at)postgreSQL(dot)org
> [mailto:owner-pgsql-interfaces(at)postgreSQL(dot)org]On Behalf Of Tom Lane
> Sent: Friday, July 23, 1999 9:54 AM
> To: Zakkr
> Cc: pgsql-interfaces
> Subject: Re: [INTERFACES] SPI_exec vs. CREATE/DROP RULE 
> 
> 
> Zakkr <zakkr(at)zf(dot)jcu(dot)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...
> 

Sorry,I missed the change of "CREATE RULE". 
Here is a patch.

Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp

*** backend/rewrite/rewriteDefine.c.orig	Wed May 26 16:04:41 1999
--- backend/rewrite/rewriteDefine.c	Fri Jul 23 11:22:09 1999
***************
*** 131,137 ****
  			rulname, evtype, eventrel_oid, evslot_index, actionbuf,
  			qualbuf, is_instead);
  
! 	pg_exec_query_acl_override(rulebuf);
  
  	return LastOidProcessed;
  }
--- 131,137 ----
  			rulname, evtype, eventrel_oid, evslot_index, actionbuf,
  			qualbuf, is_instead);
  
! 	pg_exec_query_dest(rulebuf, None, true);
  
  	return LastOidProcessed;
  }
 

In response to

pgsql-interfaces by date

Next:From: Dave PageDate: 1999-07-23 07:20:38
Subject: RE: [INTERFACES] libpq and VB
Previous:From: Colin McCormackDate: 1999-07-23 02:19:02
Subject: New asynchronous tcl postgresql interface

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group