Message-ID: <gh-pgjdbc-pgjdbc-4036-c4294047453@github.com>
From: "x4m (@x4m)" <noreply+x4m@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 22 Apr 2026 06:26:13 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #4036: Add DNS SRV discovery via jdbc:postgresql+srv:// URL scheme
In-Reply-To: <gh-pgjdbc-pgjdbc-4036@github.com>
References: <gh-pgjdbc-pgjdbc-4036@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: x4m
X-GitHub-Comment-Id: 4294047453
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 4036
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/4036#issuecomment-4294047453
Content-Type: text/plain; charset=utf-8

The plugin API from #3367 doesn't exist yet, so adopting it would block this feature. More importantly, SRV is orthogonal to what #3367 is designed for: dynamic load balancing, connection draining, per-host timeouts, and lifecycle callbacks (registerSuccess, registerFailure, registerDisconnect). SRV needs none of that - it's a one-shot host expansion at connect time, backed by an IETF standard (RFC 2782). I'm proposing this across the PostgreSQL driver ecosystem (pgx, npgsql, libpq) for the same reason: it's a standard building block that belongs to a driver.