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-20T11:42:13Z

Lists: pgsql-hackers

Attachments

v5-0001-Support-sending-Close-messages-from-libpq.patch (application/octet-stream) patch v5-0001

On Tue, 20 Jun 2023 at 06:18, Michael Paquier <michael@paquier.xyz> wrote:
> The amount of duplication between the describe and close paths
> concerns me a bit.  Should PQsendClose() and PQsendDescribe() be
> merged into a single routine (say PQsendCommand), that uses a message
> type for pqPutMsgStart and a queryclass as extra arguments?

Done (I called it PQsendTypedCommand)

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