Re: Deleting prepared statements from libpq.
Jelte Fennema <me@jeltef.nl>
From: Jelte Fennema <me@jeltef.nl>
To: Michael Paquier <michael@paquier.xyz>
Cc: jian he <jian.universality@gmail.com>,
Dmitry Igrishin <dmitigr@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Daniele Varrazzo <daniele.varrazzo@gmail.com>
Date: 2023-06-19T09:50:09Z
Lists: pgsql-hackers
Attachments
- v3-0001-Support-sending-Close-messages-from-libpq.patch (application/x-patch) patch v3-0001
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
Commits
-
libpq: Add support for Close on portals and statements
- 28b572656184 17.0 landed
-
Fix incorrect error message in libpq_pipeline
- 451ca5c1e699 14.9 landed
- 4fd633df5080 15.4 landed
- f69a7f08fd01 16.0 landed