Re: request for database identifier in the startup packet

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Dave Cramer <davecramer(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: request for database identifier in the startup packet
Date: 2024-05-09 13:55:27
Message-ID: CAKFQuwYDm_stMLhFHkGQrFD6VA-udWshSK8tmf0xdLUKJOzWkA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thursday, May 9, 2024, Dave Cramer <davecramer(at)gmail(dot)com> wrote:

> Greetings,
>
> The JDBC driver is currently keeping a per connection cache of types in
> the driver. We are seeing cases where the number of columns is quite high.
> In one case Prevent fetchFieldMetaData() from being run when unnecessary.
> · Issue #3241 · pgjdbc/pgjdbc (github.com)
> <https://github.com/pgjdbc/pgjdbc/issues/3241> 2.6 Million columns.
>
> If we knew that we were connecting to the same database we could use a
> single cache across connections.
>
> I think we would require a server/database identifier in the startup
> message.
>

I feel like pgbouncer ruins this plan.

But maybe you can construct a lookup key from some combination of data
provided by these functions:
https://www.postgresql.org/docs/current/functions-info.html#FUNCTIONS-INFO-SESSION

David J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2024-05-09 14:13:14 Re: Set appropriate processing mode for auxiliary processes.
Previous Message Bruce Momjian 2024-05-09 13:48:41 Re: First draft of PG 17 release notes