Message-ID: <gh-pgjdbc-pgjdbc-3062-c4487175649@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 19 May 2026 11:14:09 +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: 4487175649
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-4487175649
Content-Type: text/plain; charset=utf-8

> What I meant was to ask whether SQLData transparently decodes both binary and text encodings

SQLData will transparently encode and decode both.
It would prefer binary encodings by default unless user explicitly configures "disable binary encoding for type ABC".
Normally, users should not configure `binaryTransferDisable`. The property is there for workarounds only.

---

For "simple connection protocol" e.g. replication connection, binary transfer is not available, so SQLData would resort to text encodings. That is an edge case though.