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 72aeed7a-8a4c-286f-39f4-6ea4c280aa1e@wi3ck.info
Whole thread Raw
In response to Re: Named Prepared statement problems and possible solutions  (Jan Wieck <jan@wi3ck.info>)
Responses Re: Named Prepared statement problems and possible solutions
List pgsql-hackers
On 6/8/23 09:53, Jan Wieck wrote:
> On 6/8/23 09:21, Dave Cramer wrote:
> 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.

Another problem that complicates doing it in the server is that the 
information require to (re-)prepare a statement in a backend that 
currently doesn't have it needs to be kept in shared memory. This 
includes the query string itself. Doing that without shared memory in a 
pooler that is multi-threaded or based on async-IO is much simpler and 
allows for easy ballooning.


Jan




pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: generic plans and "initial" pruning
Next
From: Greg Stark
Date:
Subject: Re: Let's make PostgreSQL multi-threaded