Horton

Re: Deleting prepared statements from libpq.

jian he <jian.universality@gmail.com>

View thread View on postgr.es
From: jian he <jian.universality@gmail.com>
To: Jelte Fennema <me@jeltef.nl>
Cc: Michael Paquier <michael@paquier.xyz>, Dmitry Igrishin <dmitigr@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Daniele Varrazzo <daniele.varrazzo@gmail.com>
Date: 2023-06-19T12:17:41Z
Lists: pgsql-hackers 
On Mon, Jun 19, 2023 at 5:50 PM Jelte Fennema <me@jeltef.nl> wrote:
>
> On Mon, 19 Jun 2023 at 11:44, Jelte Fennema <me@jeltef.nl> wrote:
> > Done
>
> Now with the actual attachment.
>
> PS. Another connection pooler (PgCat) now also supports prepared
> statements, but only using Close not DEALLOCATE:
> https://postgresml.org/blog/making-postgres-30-percent-faster-in-production

it works on my local machine.
I am not sure the following two following function comments are right....

/*
 * PQclosePrepared
 *   Obtain information about a previously prepared statement
 * ......

/*
 * PQclosePortal
 *   Obtain information about a previously created portal
 * ....

Commits

  1. libpq: Add support for Close on portals and statements

  2. Fix incorrect error message in libpq_pipeline