Re: Named Prepared statement problems and possible solutions - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: Named Prepared statement problems and possible solutions
Date
Msg-id b53a3ec5-9240-259c-19bb-0a9996a7535b@wi3ck.info
Whole thread Raw
In response to Re: Named Prepared statement problems and possible solutions  (Dave Cramer <davecramer@gmail.com>)
Responses Re: Named Prepared statement problems and possible solutions
Re: Named Prepared statement problems and possible solutions
List pgsql-hackers
On 6/8/23 09:21, Dave Cramer wrote:
> 
> 
> On Thu, Jun 8, 2023 at 8:43 AM Jan Wieck <jan@wi3ck.info 
> <mailto:jan@wi3ck.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



pgsql-hackers by date:

Previous
From: Konstantin Knizhnik
Date:
Subject: Re: Let's make PostgreSQL multi-threaded
Next
From: Robert Haas
Date:
Subject: Re: Let's make PostgreSQL multi-threaded