Message-ID: <gh-pgjdbc-pgjdbc-3780-c3210695570@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 21 Aug 2025 13:49:01 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3780: fix: avoid NullPointerException when cancelling a query if cancel key is not known yet
In-Reply-To: <gh-pgjdbc-pgjdbc-3780@github.com>
References: <gh-pgjdbc-pgjdbc-3780@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: davecramer
X-GitHub-Comment-Id: 3210695570
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3780
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3780#issuecomment-3210695570
Content-Type: text/plain; charset=utf-8

> Stacktrace at [#3530 (comment)](https://github.com/pgjdbc/pgjdbc/issues/3530#issuecomment-2948773054) indicates there are cases when the cancelKey is null.

Not debating the existence, just curious how it can happen. Not really important. Just curiousity