Message-ID: <gh-pgjdbc-pgjdbc-3728-c3150230184@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 04 Aug 2025 11:29:51 +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: vlsi
X-GitHub-Comment-Id: 3150230184
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-3150230184
Content-Type: text/plain; charset=utf-8

@haster , thanks so much for testing this, and it is really painful for me to test in prod what could be tested in CI. One of the options that might be useful is to configure pgpool2 and make tests work through pgool2 -> test database.

Frankly speaking, I have previously tried adding pgpool2 to our [docker-compose.yml](https://github.com/pgjdbc/pgjdbc/blob/9370b33fcce0f5605ccad500e7de9f4bf939e085/docker/postgres-server/docker-compose.yml), however, it was harder than I thought it would be. Do you think you could help with adding pgpool2 to `docker-compose.yml`? I expect it might be fine to use it for a subset of the tests only, however, it would be nice to add those types of tests as well.