Re: Deleting prepared statements from libpq.

From: Jelte Fennema <me(at)jeltef(dot)nl>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, 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-20 11:42:13
Message-ID: CAGECzQTwEMQL9yEgMLyj3DLWSNaXSYcbge5RomXDvNHDgEp0uA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 20 Jun 2023 at 06:18, Michael Paquier <michael(at)paquier(dot)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)

Attachment Content-Type Size
v5-0001-Support-sending-Close-messages-from-libpq.patch application/octet-stream 22.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Russell Foster 2023-06-20 11:49:52 Re: Postgres v15 windows bincheck regression test failures
Previous Message Joel Jacobson 2023-06-20 10:59:32 Re: Do we want a hashset type?