Re: request for database identifier in the startup packet - Mailing list pgsql-hackers

From Robert Haas
Subject Re: request for database identifier in the startup packet
Date
Msg-id CA+TgmobquXNxYLFk4e6QbtAe2fp+1U_Fj1TcL17O+U5OsxLCfA@mail.gmail.com
Whole thread Raw
In response to request for database identifier in the startup packet  (Dave Cramer <davecramer@gmail.com>)
Responses Re: request for database identifier in the startup packet
List pgsql-hackers
On Thu, May 9, 2024 at 8:06 AM Dave Cramer <davecramer@gmail.com> wrote:
> The JDBC driver is currently keeping a per connection cache of types in the driver. We are seeing cases where the
numberof columns is quite high. In one case Prevent fetchFieldMetaData() from being run when unnecessary. · Issue #3241
·pgjdbc/pgjdbc (github.com) 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 understand the desire to share the cache, but not why that would
require any kind of change to the wire protocol.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: First draft of PG 17 release notes
Next
From: "David G. Johnston"
Date:
Subject: Is there an undocumented Syntax Check in Meson?