pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feed[pgjdbc/pgjdbc] PR #3780: fix: avoid NullPointerException when cancelling a query if cancel key is not known yet
6+ messages / 3 participants
[nested] [flat]
* [pgjdbc/pgjdbc] PR #3780: fix: avoid NullPointerException when cancelling a query if cancel key is not known yet
@ 2025-08-21 13:32 "vlsi (@vlsi)" <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: vlsi (@vlsi) @ 2025-08-21 13:32 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
Previously, and unknown cancel key might cause a NPE.
See https://github.com/pgjdbc/pgjdbc/issues/3530#issuecomment-2948773054
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3780: fix: avoid NullPointerException when cancelling a query if cancel key is not known yet
@ 2025-08-21 13:35 "davecramer (@davecramer)" <[email protected]>
4 siblings, 0 replies; 6+ messages in thread
From: davecramer (@davecramer) @ 2025-08-21 13:35 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
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?
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3780: fix: avoid NullPointerException when cancelling a query if cancel key is not known yet
@ 2025-08-21 13:45 "vlsi (@vlsi)" <[email protected]>
4 siblings, 0 replies; 6+ messages in thread
From: vlsi (@vlsi) @ 2025-08-21 13:45 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
Stacktrace at https://github.com/pgjdbc/pgjdbc/issues/3530#issuecomment-2948773054 indicates there are cases when the cancelKey is null.
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3780: fix: avoid NullPointerException when cancelling a query if cancel key is not known yet
@ 2025-08-21 13:49 "davecramer (@davecramer)" <[email protected]>
4 siblings, 0 replies; 6+ messages in thread
From: davecramer (@davecramer) @ 2025-08-21 13:49 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
> 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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3780: fix: avoid NullPointerException when cancelling a query if cancel key is not known yet
@ 2025-08-21 14:47 "vlsi (@vlsi)" <[email protected]>
4 siblings, 0 replies; 6+ messages in thread
From: vlsi (@vlsi) @ 2025-08-21 14:47 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
Frankly, I've no idea how is it possible.
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3780: fix: avoid NullPointerException when cancelling a query if cancel key is not known yet
@ 2025-08-22 08:08 "krystianzybala (@krystianzybala)" <[email protected]>
4 siblings, 0 replies; 6+ messages in thread
From: krystianzybala (@krystianzybala) @ 2025-08-22 08:08 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
Nice job!
@vlsi Can I ask you, are you going to make release soon? What is ETA for new release?
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2025-08-22 08:08 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-08-21 13:32 [pgjdbc/pgjdbc] PR #3780: fix: avoid NullPointerException when cancelling a query if cancel key is not known yet "vlsi (@vlsi)" <[email protected]>
2025-08-21 13:35 ` "davecramer (@davecramer)" <[email protected]>
2025-08-21 13:45 ` "vlsi (@vlsi)" <[email protected]>
2025-08-21 13:49 ` "davecramer (@davecramer)" <[email protected]>
2025-08-21 14:47 ` "vlsi (@vlsi)" <[email protected]>
2025-08-22 08:08 ` "krystianzybala (@krystianzybala)" <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox