Message-ID: <gh-pgjdbc-pgjdbc-3062-c4485610177@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 19 May 2026 07:56:29 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3062: feat: type cache rework, codec API, and composite-type round-trip
In-Reply-To: <gh-pgjdbc-pgjdbc-3062@github.com>
References: <gh-pgjdbc-pgjdbc-3062@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 4485610177
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3062
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3062#issuecomment-4485610177
Content-Type: text/plain; charset=utf-8

> I'll try to work with your branch

I just noticed the array support is incomplete (yet it somehow works). Arrays still rely on old ArrayEncoding/ArrayDecoding. I am going to harmonize it.

>Even if this flag isn't set, SQLData can be used for all types, with more overhead?

RECORD is not in the driver's SUPPORTED_BINARY_OIDS default set yet, so the test must opt in via binaryTransferEnable=RECORD to exercise the binary path;

I guess one more TODO for the PR is to enable binary transfer by default for all the types pgjdbc can decode.