libpq and SPI

From: "Gerald L(dot) Gay" <glgay(at)pass(dot)korea(dot)army(dot)mil>
To: "Postgres Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: libpq and SPI
Date: 1999-02-25 05:02:58
Message-ID: 01be01be607c$1cf40d40$9a028a8f@2isdt54.korea.army.mil
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I have seen what I concider to be a bug in either the libpq library or
in the backend. To see the effects, first, install the execq() function
from the SPI section of the Programmers Guide. Then do this in psql:

template1=> select execq('create user fred', 1);
Backend sent D message without prior T

At this point psql will hang. I have a patch for libpq that fixes this
but I am not sure if this is the right place for it. My questions are: Is
it not reasonable to run "utility" queries from inside SPI? Is the problem
in the client-side libpq interface or should something be done at the server
end? If anyone is interested, I can explain why I want to do this.

Any advice would be greatly appreciated.

Jerry

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-02-25 05:15:00 Current tree is busted
Previous Message Hiroshi Inoue 1999-02-25 01:57:50 RE: [HACKERS] copyObject() ?