| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Dmitry Igrishin <dmitigr(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Deleting prepared statements from libpq. |
| Date: | 2016-05-26 01:22:40 |
| Message-ID: | CAMsr+YEsk0z6rctRiw54CkAehosPternSdrws+f8LKMd4b4MHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 25 May 2016 at 18:05, Dmitry Igrishin <dmitigr(at)gmail(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2016-05-26 01:57:01 | Re: Parallel pg_dump's error reporting doesn't work worth squat |
| Previous Message | Craig Ringer | 2016-05-26 01:19:42 | Re: Inheritance |