libpq and SPI

From: "Gerald L(dot) Gay" <glgay(at)pass(dot)korea(dot)army(dot)mil>
To: "Postgres Interfaces" <pgsql-interfaces(at)hub(dot)org>
Subject: libpq and SPI
Date: 1999-02-25 01:00:09
Message-ID: 018201be605a$30ad00c0$9a028a8f@2isdt54.korea.army.mil
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

Hi,

I sent an email a few days ago and I haven't seen any response yet.
Basically, the problem is, if you do any "utility" queries inside of a SPI
function, libpq will lock up. You can see this by installing the execq()
example from the Programmer's Guide and doing the following from psql:

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

And you will not get a prompt back. I was looking for thoughts on this.
Is it not reasonable to allow utility calls inside SPI? Should the backend
be sending data through libpq differently? Or should the client-side libpq
be handling this better? I patched the client-side libpq since I didn't
want to go messing with the backend.

Should this discussion be on a different mailing list?

Any ideas would be greatly appreciated.

Jerry

Browse pgsql-interfaces by date

  From Date Subject
Next Message Shoku Yanagawa 1999-02-25 01:11:33 Re: [INTERFACES] problems with pgaccess
Previous Message Peter T Mount 1999-02-24 23:16:26 Re: [INTERFACES] Problem with ODBC