pg.ddx.io  GitHub: pgjdbc/pgjdbc (issues + PRs as email threads)  
help / color / mirror / Atom feed
From: sehrope (@sehrope) <noreply+sehrope@github.com>
To: pgjdbc/pgjdbc <noreply+pgjdbc-pgjdbc@github.com>
Subject: Re: [pgjdbc/pgjdbc] PR #4331: fix(copy): keep the COPY active when a read times out
Date: Fri, 21 Aug 2026 13:09:34 +0000
Message-ID: <gh-pgjdbc-pgjdbc-4331-c5370195036@github.com> (raw)
In-Reply-To: <gh-pgjdbc-pgjdbc-4331@github.com>
References: <gh-pgjdbc-pgjdbc-4331@github.com>

A few of us have been away over the summer and this isn't the only PR that's gone unlooked at. Nothing personal in the delay.

That said, this is not a trivial change and three weeks of no comments isn't the same as approval. This touches the COPY lock and the connection-failure path in QueryExecutorImpl, which is exactly the area where the last fix caused this regression, so it needs someone to actually read it before it goes in. I'd rather it wait a bit longer than merge unreviewed.

I'll try to get to it this week. If someone else can take a look sooner, please do.


view thread (14+ messages)  latest in thread

Message-ID: <gh-pgjdbc-pgjdbc-4331-c5370195036@github.com>
Permalink:  ../gh-pgjdbc-pgjdbc-4331-c5370195036@github.com/

 · 


This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox