Message-ID: <gh-pgjdbc-pgjdbc-3728-c3150218161@github.com>
From: "haster (@haster)" <noreply+haster@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 04 Aug 2025 11:25:34 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3728: fix: ensure extended protocol messages end with Sync message
In-Reply-To: <gh-pgjdbc-pgjdbc-3728@github.com>
References: <gh-pgjdbc-pgjdbc-3728@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: haster
X-GitHub-Comment-Id: 3150218161
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3728
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3728#issuecomment-3150218161
Content-Type: text/plain; charset=utf-8

Hey, due to an error on my end we unfortunately ran with the incorrect driver for our first week of testing, but the 'good' news is that I quickly noticed that while checking the logs. After fixing that last tuesday we now run with the correct (patched) driver and I haven't seen this error reoccur so far.

We still need to wait longer to be more sure, since it is a testing environment with nowhere near production-like usage patterns, but things are looking good on our end.