pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: vlsi (@vlsi) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] PR #4075: docs: restructure site, compatibility page, changelog-driven releases
Date: Thu, 21 May 2026 12:28:44 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
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).
view thread (64+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] PR #4075: docs: restructure site, compatibility page, changelog-driven releases
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox