Re: Deleting prepared statements from libpq. - Mailing list pgsql-hackers

From jian he
Subject Re: Deleting prepared statements from libpq.
Date
Msg-id CACJufxE1JfecGKL7oCS7VGFkEq0UKhHLnoDJ=QkEkCQnWJy1mw@mail.gmail.com
Whole thread Raw
In response to Re: Deleting prepared statements from libpq.  (Jelte Fennema <me@jeltef.nl>)
Responses Re: Deleting prepared statements from libpq.
List 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
 * ....



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Do we want a hashset type?
Next
From: Jelte Fennema
Date:
Subject: Re: Deleting prepared statements from libpq.