On Tue, 31 Mar 2026 at 01:17, Tatsuo Ishii <ishii@postgresql.org> wrote:
> Interesting. In Pgpool-II case, client disconnection is not a problem,
> the connection to PostgreSQL is kept open anyway (if connection
> expiration is not set). Probably this is because Pgpool-II only
> supports "session level" connection pooling.
I guess, I was not clear. Because the same problem exists for
Pgpool-II. When pgpool forwards the message to the client, the client
will disconnect from pgpool. But if connection_life_time is not
reached (and by default this is unlimited) pgpool will not disconnect
from the postgres server. So the postgres server has not actually
achieved the intended goal, but the client still disconnected for no
benefit, only downsides.
Maybe the problem is not too bad, i.e. it will cause some unnecessary
disconnects from the client, but it shouldn't cause big problems. So
maybe the ParameterStatus approach is worth exploring again (I
remember I ran into some problems, due to us normally only sending
ParameterStatus at the end of a query, but I'm pretty sure that can be
worked around somehow).
