Re: [HACKERS] Deleting prepared statements from libpq.

2016-05-25 Thread Craig Ringer 
On 25 May 2016 at 18:05, Dmitry Igrishin  wrote:

> Hello,
>
> According to
>
> https://www.postgresql.org/docs/current/static/protocol-flow.html#PROTOCOL-FLOW-EXT-QUERY
> there are Close message for closing prepared statements or portals, but
> according to
>
> https://www.postgresql.org/docs/current/static/libpq-exec.html#LIBPQ-PQPREPARE
> "there is no libpq function for deleting a prepared statement".
>
> Could you tell me please, what is the reason for this?
>

Nobody's implemented it.

A patch to add PQclosePrepared and PQsendClosePrepared would be welcome. At
least, I think so...


-- 
 Craig Ringer   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

Re: [HACKERS] Deleting prepared statements from libpq.

2016-05-25 Thread Dmitry Igrishin 
2016-05-25 16:50 GMT+03:00 Tom Lane :

> Dmitry Igrishin  writes:
> > "there is no libpq function for deleting a prepared statement".
> > Could you tell me please, what is the reason for this?
>
> You don't really need one, since you can just use DEALLOCATE.
>
Yes, but there are also Parse(F) message, while anybody can just use
PREPARE.

-- 
// Dmitry.

Re: [HACKERS] Deleting prepared statements from libpq.

2016-05-25 Thread Tom Lane 
Dmitry Igrishin  writes:
> "there is no libpq function for deleting a prepared statement".
> Could you tell me please, what is the reason for this?

You don't really need one, since you can just use DEALLOCATE.

regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers