Message-ID: <gh-pgjdbc-pgjdbc-4075-c4508491131@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 21 May 2026 13:00:01 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #4075: docs: restructure site, compatibility page, changelog-driven releases
In-Reply-To: <gh-pgjdbc-pgjdbc-4075@github.com>
References: <gh-pgjdbc-pgjdbc-4075@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: davecramer
X-GitHub-Comment-Id: 4508491131
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 4075
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/4075#issuecomment-4508491131
Content-Type: text/plain; charset=utf-8

> Pushed a follow-up that absorbs the operational lessons from @sergiorussia's JPoint 2024 talk [PG for Java developers](https://github.com/sergiorussia/jpoint-2024-pg-for-java-developers) (in Russian) into the doc tree, with `{{< review >}}` anchors pointing back at the relevant driver source:
> 
> * **`timeouts.md`**. New _Interaction with a connection pool (HikariCP)_ section (the `loginTimeout`/`HikariConfig.connectionTimeout` asymmetry between `dataSourceClassName` and `jdbcUrl`, and the initial-fill bypass), plus _Host status tracker and `hostRecheckSeconds`_ covering the `connectTimeout`/`hostRecheckSeconds=10` default collision.
> * **`recommended-properties.md`**. New `assumeMinServerVersion` (skip a startup `SET` round-trip) and `loadBalanceHosts` entries; the existing `reWriteBatchedInserts` entry is now a short teaser that points at the new explanation page.
> * **`query/batch-inserts.md`** _(new)_. Explanation page for `reWriteBatchedInserts`: activation conditions, the power-of-two grouping, what `executeBatch()` actually returns, the `pg_stat_statements` trade-off, and a cross-link to COPY as the "I am willing to restructure the load path" alternative.
> 
> Some of the rough edges the talk surfaces are worth _fixing_ rather than just documenting; I opened **#4081** as an umbrella for that — _Timeout Semantics Overhaul for Operational Robustness_ — split into **#4082** (startup deadline model), **#4083** (secure-handshake timeout semantics) and **#4084** (multi-host retry and host-status model).

where is the follow up and how are we supposed to read the Russian talk ?