Re: Named Prepared statement problems and possible solutions

From: Dave Cramer <davecramer(at)gmail(dot)com>
To: Jan Wieck <jan(at)wi3ck(dot)info>
Cc: Konstantin Knizhnik <knizhnik(at)garret(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Named Prepared statement problems and possible solutions
Date: 2023-06-08 13:21:07
Message-ID: CADK3HH+MbfKWUjL7u6me-VY0b8LKK9QMcpSR5-=akKw7=m9_Gw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 8, 2023 at 8:43 AM Jan Wieck <jan(at)wi3ck(dot)info> wrote:

> On 6/8/23 02:15, Konstantin Knizhnik wrote:
>
> > There is a PR with support of prepared statement support to pgbouncer:
> > https://github.com/pgbouncer/pgbouncer/pull/845
> > any feedback, reviews and suggestions are welcome.
>
> I was about to say that the support would have to come from the pooler
> as it is possible to have multiple applications in different languages
> connecting to the same pool(s).

Why from the pooler? If it were done at the server every client could use
it?

>
> Dave

>
> --
Dave Cramer

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Konstantin Knizhnik 2023-06-08 13:27:47 Re: Named Prepared statement problems and possible solutions
Previous Message Tomas Vondra 2023-06-08 12:55:09 Parallel CREATE INDEX for BRIN indexes