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-19 09:50:09
Message-ID: CAGECzQQJWJ8ZUPSurtd5R4Zc4zwPUdWtJntA0432UZe5Vwj=Cg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Attachment Content-Type Size
v3-0001-Support-sending-Close-messages-from-libpq.patch application/x-patch 20.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2023-06-19 10:03:37 Re: Synchronizing slots from primary to standby
Previous Message jian he 2023-06-19 09:49:48 Re: Do we want a hashset type?