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

From Michael Paquier
Subject Re: Deleting prepared statements from libpq.
Date
Msg-id ZJEonC3cqUAQ+4Lu@paquier.xyz
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 02:49:44PM +0200, Jelte Fennema wrote:
> On Mon, 19 Jun 2023 at 14:17, jian he <jian.universality@gmail.com> wrote:
>> I am not sure the following two following function comments are right....
>
> They were incorrect indeed. Attached is a patch with those two updated.

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?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Making empty Bitmapsets always be NULL
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: add non-option reordering to in-tree getopt_long