| From: | Jan Wieck <jan(at)wi3ck(dot)info> |
|---|---|
| To: | Dave Cramer <davecramer(at)gmail(dot)com> |
| 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:53:02 |
| Message-ID: | b53a3ec5-9240-259c-19bb-0a9996a7535b@wi3ck.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/8/23 09:21, Dave Cramer wrote:
>
>
> On Thu, Jun 8, 2023 at 8:43 AM Jan Wieck <jan(at)wi3ck(dot)info
> <mailto: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
> <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?
The server doesn't know about all the clients of the pooler, does it? It
has no way of telling if/when a client disconnects from the pooler.
Jan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2023-06-08 13:56:37 | Re: Let's make PostgreSQL multi-threaded |
| Previous Message | Konstantin Knizhnik | 2023-06-08 13:47:48 | Re: Let's make PostgreSQL multi-threaded |