Re: Named Prepared statement problems and possible solutions

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 14:31:05
Message-ID: 72aeed7a-8a4c-286f-39f4-6ea4c280aa1e@wi3ck.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2023-06-08 14:33:26 Re: Let's make PostgreSQL multi-threaded
Previous Message Amit Langote 2023-06-08 14:23:21 Re: generic plans and "initial" pruning