| From: | jian he <jian(dot)universality(at)gmail(dot)com> |
|---|---|
| To: | Jelte Fennema <me(at)jeltef(dot)nl> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Dmitry Igrishin <dmitigr(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
| Subject: | Re: Deleting prepared statements from libpq. |
| Date: | 2023-06-19 12:17:41 |
| Message-ID: | CACJufxE1JfecGKL7oCS7VGFkEq0UKhHLnoDJ=QkEkCQnWJy1mw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 19, 2023 at 5:50 PM Jelte Fennema <me(at)jeltef(dot)nl> wrote:
>
> On Mon, 19 Jun 2023 at 11:44, Jelte Fennema <me(at)jeltef(dot)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
* ....
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema | 2023-06-19 12:49:44 | Re: Deleting prepared statements from libpq. |
| Previous Message | Tomas Vondra | 2023-06-19 11:59:17 | Re: Do we want a hashset type? |