pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  
help / color / mirror / Atom feed
[pgjdbc/pgjdbc] issue #4037: StatementTest fails with JDK 8
  2026-04-22 08:20 UTC  "harudini (@harudini)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #4037: StatementTest fails with JDK 8
  2026-04-22 09:22 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #4037: StatementTest fails with JDK 8
  2026-04-22 10:32 UTC  "vlsi (@vlsi)" <[email protected]>
  [3+ messages in thread]

[pgjdbc/pgjdbc] PR #4038: fix: keep LazyCleanerImpl cleanup task alive across transient empty queue
  2026-04-22 10:15 UTC  "vlsi (@vlsi)" <[email protected]>

[pgjdbc/pgjdbc] PR #4036: Add DNS SRV discovery via jdbc:postgresql+srv:// URL scheme
  2026-04-21 18:38 UTC  "x4m (@x4m)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #4036: Add DNS SRV discovery via jdbc:postgresql+srv:// URL scheme
  2026-04-22 05:54 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #4036: Add DNS SRV discovery via jdbc:postgresql+srv:// URL scheme
  2026-04-22 06:26 UTC  "x4m (@x4m)" <[email protected]>
  [3+ messages in thread]

[pgjdbc/pgjdbc] PR #4035: style: replace @exception with @throws in getBoolean javadoc
  2026-04-20 16:10 UTC  "vlsi (@vlsi)" <[email protected]>

[pgjdbc/pgjdbc] issue #3955: The value of backend_xmin has different transaction behaviors in JDBC and PSQL
  2026-03-11 12:34 UTC  "frlzk (@frlzk)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3955: The value of backend_xmin has different transaction behaviors in JDBC and PSQL
  2026-04-20 13:52 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3955: The value of backend_xmin has different transaction behaviors in JDBC and PSQL
  2026-04-20 13:54 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3955: The value of backend_xmin has different transaction behaviors in JDBC and PSQL
  2026-04-20 15:24 UTC  "davecramer (@davecramer)" <[email protected]>
  [4+ messages in thread]

[pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2014-10-02 13:03 UTC  "ringerc (@ringerc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2014-10-02 13:16 UTC  "ringerc (@ringerc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2014-10-02 13:53 UTC  "ringerc (@ringerc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2016-09-16 09:51 UTC  "nicolasbarbier (@nicolasbarbier)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2016-09-16 11:56 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2016-09-21 13:36 UTC  "nicolasbarbier (@nicolasbarbier)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2017-10-26 14:39 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2017-10-26 14:55 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2018-07-31 02:32 UTC  "ringerc (@ringerc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2018-07-31 02:58 UTC  "ringerc (@ringerc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2018-10-03 10:37 UTC  "sasavilic (@sasavilic)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2019-04-25 15:29 UTC  "turbanoff (@turbanoff)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2019-05-22 13:15 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2019-07-25 08:00 UTC  "zistrong (@zistrong)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2019-07-25 10:42 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2019-12-04 03:46 UTC  "oobles (@oobles)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2019-12-04 16:06 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2020-01-22 05:59 UTC  "ringerc (@ringerc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2020-01-22 06:10 UTC  "ringerc (@ringerc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2020-01-22 10:49 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2020-04-01 16:50 UTC  "turbanoff (@turbanoff)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2020-07-20 23:27 UTC  "sposerina (@sposerina)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2020-07-21 00:45 UTC  "oobles (@oobles)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2020-08-04 11:17 UTC  "codingsemen (@codingsemen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2021-04-26 09:07 UTC  "bigfacewo (@bigfacewo)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2022-06-07 12:07 UTC  "rutchkiwi (@rutchkiwi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2022-06-07 12:09 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2022-06-07 12:13 UTC  "rutchkiwi (@rutchkiwi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2022-06-07 12:22 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2022-06-07 13:00 UTC  "rutchkiwi (@rutchkiwi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2022-06-07 21:35 UTC  "rbygrave (@rbygrave)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2022-06-08 15:42 UTC  "rutchkiwi (@rutchkiwi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2024-06-12 15:59 UTC  "MosheElisha (@MosheElisha)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2024-06-12 22:35 UTC  "ringerc (@ringerc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2026-04-13 11:34 UTC  "bilalshehata (@bilalshehata)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
  2026-04-14 21:54 UTC  "vlsi (@vlsi)" <[email protected]>
  [36+ messages in thread]

[pgjdbc/pgjdbc] PR #4034: chore(deps): update actions/create-github-app-token action to v3
  2026-04-13 21:15 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4033: chore(deps): update actions/configure-pages action to v6
  2026-04-13 21:15 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4032: chore(deps): update actions/checkout action to v6
  2026-04-13 20:16 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4031: fix(deps): update dependency org.openrewrite.rewrite:org.openrewrite.rewrite.gradle.plugin to v7.30.0
  2026-04-13 20:16 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4030: fix(deps): update dependency com.google.errorprone:error_prone_core to v2.49.0
  2026-04-13 17:03 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4029: fix(deps): update checkerframework to v3.55.1
  2026-04-13 15:17 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4028: fix(deps): update dependency net.bytebuddy:byte-buddy-parent to v1.18.8 - autoclosed
  2026-04-13 15:17 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4027: fix: drain CopyOut messages after cancel to restore connection usability
  2026-04-13 14:39 UTC  "anuragg-saxenaa (@anuragg-saxenaa)" <[email protected]>

[pgjdbc/pgjdbc] PR #4026: chore(deps): update plugin com.gradle.develocity to v4.4.0
  2026-04-13 11:09 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4025: chore(deps): update github/codeql-action action to v3.35.1
  2026-04-13 11:09 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4024: fix(deps): update dependency org.roaringbitmap:roaringbitmap to v1.6.14
  2026-04-13 10:51 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4023: fix(deps): update dependency net.bytebuddy:byte-buddy-parent to v1.18.8-jdk5
  2026-04-13 10:51 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4022: fix(deps): update dependency net.bytebuddy:byte-buddy-agent to v1.18.8
  2026-04-13 09:41 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4021: fix(deps): update dependency com.gradleup.shadow:com.gradleup.shadow.gradle.plugin to v9.4.1
  2026-04-13 09:41 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4020: chore(deps): update plugin biz.aqute.bnd.builder to v7.2.3
  2026-04-13 04:33 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4019: chore(deps): update dependency sbt/sbt to v1.12.9
  2026-04-13 04:33 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4018: chore(deps): update codecov/codecov-action action to v5.5.4
  2026-04-13 01:01 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #4017: chore(deps): update ubuntu:24.04 docker digest to 84e77de
  2026-04-13 01:01 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] issue #4015: receiveTupleV3 allocates huge byte[] due to misread 4-byte field length under high concurrency
  2026-04-10 10:42 UTC  "duwenice (@duwenice)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #4015: receiveTupleV3 allocates huge byte[] due to misread 4-byte field length under high concurrency
  2026-04-10 11:15 UTC  "davecramer (@davecramer)" <[email protected]>
  [2+ messages in thread]


[next (older)]

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