Re: request for database identifier in the startup packet

From: Robert Haas <robertmhaas(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 16:22:37
Message-ID: CA+TgmobquXNxYLFk4e6QbtAe2fp+1U_Fj1TcL17O+U5OsxLCfA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 9, 2024 at 8:06 AM Dave Cramer <davecramer(at)gmail(dot)com> wrote:
> 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) 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2024-05-09 16:23:37 Is there an undocumented Syntax Check in Meson?
Previous Message Andrew Dunstan 2024-05-09 16:10:11 Re: First draft of PG 17 release notes