From: | Jelte Fennema <me(at)jeltef(dot)nl> |
---|---|
To: | jian he <jian(dot)universality(at)gmail(dot)com> |
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:49:44 |
Message-ID: | CAGECzQRP5Bf2EraVUzYF=tRvQVsq6fm2mTb4zbpEYk+hpqe-Ww@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 19 Jun 2023 at 14:17, jian he <jian(dot)universality(at)gmail(dot)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.
On Mon, 19 Jun 2023 at 14:17, jian he <jian(dot)universality(at)gmail(dot)com> wrote:
>
> 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
> * ....
Attachment | Content-Type | Size |
---|---|---|
v4-0001-Support-sending-Close-messages-from-libpq.patch | application/octet-stream | 20.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2023-06-19 12:59:01 | Re: Do we want a hashset type? |
Previous Message | jian he | 2023-06-19 12:17:41 | Re: Deleting prepared statements from libpq. |