Message-ID: <gh-pgjdbc-pgjdbc-3780-c3210635885@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 21 Aug 2025 13:35:59 +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: 3210635885
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-3210635885
Content-Type: text/plain; charset=utf-8

interesting, I'm still curious how cancel would have been called with a null cancel key since the key is sent pretty early in the connection startup?