pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feed[pgjdbc/pgjdbc] PR #4013: fix: initialize maxBufferedRecvBytes from actual socket receive buffe…
2026-04-08 03:37 UTC "bilalshehata (@bilalshehata)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #4013: fix: initialize maxBufferedRecvBytes from actual socket receive buffe…
2026-04-08 09:43 UTC "bilalshehata (@bilalshehata)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #4013: fix: initialize maxBufferedRecvBytes from actual socket receive buffe…
2026-04-08 09:58 UTC "bilalshehata (@bilalshehata)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #4013: fix: initialize maxBufferedRecvBytes from actual socket receive buffe…
2026-04-08 09:59 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #4013: fix: initialize maxBufferedRecvBytes from actual socket receive buffe…
2026-04-08 10:00 UTC "bilalshehata (@bilalshehata)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #4013: fix: initialize maxBufferedRecvBytes from actual socket receive buffe…
2026-04-08 10:03 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #4013: fix: initialize maxBufferedRecvBytes from actual socket receive buffe…
2026-04-08 11:46 UTC "bilalshehata (@bilalshehata)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #4013: fix: initialize maxBufferedRecvBytes from actual socket receive buffe…
2026-04-08 12:16 UTC "bilalshehata (@bilalshehata)" <[email protected]>
[8+ messages in thread]
[pgjdbc/pgjdbc] issue #3726: BatchInsert + generatedKeys will cause insert block in DB
2025-07-13 14:32 UTC "wufengke (@wufengke)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3726: BatchInsert + generatedKeys will cause insert block in DB
2025-07-13 15:44 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3726: BatchInsert + generatedKeys will cause insert block in DB
2025-07-13 16:04 UTC "wufengke (@wufengke)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3726: BatchInsert + generatedKeys will cause insert block in DB
2025-07-13 17:24 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3726: BatchInsert + generatedKeys will cause insert block in DB
2025-07-14 13:41 UTC "wufengke (@wufengke)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3726: BatchInsert + generatedKeys will cause insert block in DB
2025-07-14 13:49 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3726: BatchInsert + generatedKeys will cause insert block in DB
2026-04-08 04:47 UTC "bilalshehata (@bilalshehata)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3726: BatchInsert + generatedKeys will cause insert block in DB
2026-04-08 09:09 UTC "davecramer (@davecramer)" <[email protected]>
[8+ messages in thread]
Re: [pgjdbc/pgjdbc] PR #1977: Group startup statements
2026-04-04 09:45 UTC "codecov-commenter (@codecov-commenter)" <[email protected]>
[pgjdbc/pgjdbc] PR #1637: Only allow binary transfer for those Oids that the pgjdbc currently s…
2019-12-05 15:09 UTC "mahmoudbahaa (@mahmoudbahaa)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #1637: Only allow binary transfer for those Oids that the pgjdbc currently s…
2019-12-05 15:25 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #1637: Only allow binary transfer for those Oids that the pgjdbc currently s…
2019-12-05 17:52 UTC "codecov-io (@codecov-io)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #1637: Only allow binary transfer for those Oids that the pgjdbc currently s…
2019-12-06 08:56 UTC "mahmoudbahaa (@mahmoudbahaa)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #1637: Only allow binary transfer for those Oids that the pgjdbc currently s…
2026-04-01 20:36 UTC "codecov-commenter (@codecov-commenter)" <[email protected]>
[5+ messages in thread]
[pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 13:56 UTC "embuc (@embuc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 14:08 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 14:22 UTC "embuc (@embuc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 14:30 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 14:54 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 15:16 UTC "embuc (@embuc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 15:28 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 15:35 UTC "embuc (@embuc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 15:47 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 15:59 UTC "embuc (@embuc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 16:02 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 16:26 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 18:14 UTC "embuc (@embuc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 18:20 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 18:29 UTC "embuc (@embuc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 18:43 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 18:45 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-09 19:17 UTC "embuc (@embuc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-10 10:35 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-10 10:40 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-10 11:31 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-10 11:35 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-10 19:20 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-11 10:16 UTC "embuc (@embuc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-11 10:19 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-11 10:20 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-11 12:07 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-11 12:46 UTC "embuc (@embuc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-11 12:58 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-11 13:02 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-11 13:23 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-11 13:59 UTC "bokken (@bokken)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-11 15:15 UTC "embuc (@embuc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-11 16:02 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-11 16:16 UTC "embuc (@embuc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-11 16:20 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-11 16:54 UTC "embuc (@embuc)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-11 17:22 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-01-18 13:16 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-12-02 11:13 UTC "bataroland (@bataroland)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-12-02 11:56 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-12-02 16:09 UTC "bataroland (@bataroland)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-12-12 06:49 UTC "bataroland (@bataroland)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2024-12-12 10:15 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2025-01-29 15:20 UTC "bataroland (@bataroland)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2025-01-29 20:39 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2025-02-27 05:57 UTC "bataroland (@bataroland)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2025-02-27 12:57 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
2026-03-31 06:06 UTC "vlsi (@vlsi)" <[email protected]>
[49+ messages in thread]
[pgjdbc/pgjdbc] PR #3752: chore: bump Gradle to 9.0
2025-08-05 09:29 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3752: chore: bump Gradle to 9.0
2026-03-29 11:13 UTC "vlsi (@vlsi)" <[email protected]>
[2+ messages in thread]
[pgjdbc/pgjdbc] issue #2325: Support pipelining queries
2021-10-27 09:33 UTC "kustodian (@kustodian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
2021-10-27 09:36 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
2021-12-17 14:00 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
2021-12-17 16:39 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
2021-12-17 16:55 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
2022-07-20 14:31 UTC "ebrandsberg (@ebrandsberg)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
2026-02-11 22:58 UTC "beikov (@beikov)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
2026-02-12 10:43 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
2026-03-27 10:37 UTC "beikov (@beikov)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
2026-03-27 11:19 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
2026-03-27 11:25 UTC "beikov (@beikov)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
2026-03-27 15:00 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
2026-03-27 15:01 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
2026-03-27 15:25 UTC "beikov (@beikov)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
2026-03-27 16:55 UTC "vlsi (@vlsi)" <[email protected]>
[15+ messages in thread]
[pgjdbc/pgjdbc] PR #4010: [#2325] Execute queries as pipelined when running on virtual thread
2026-03-26 17:35 UTC "beikov (@beikov)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #4010: [#2325] Execute queries as pipelined when running on virtual thread
2026-03-27 11:59 UTC "beikov (@beikov)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #4010: [#2325] Execute queries as pipelined when running on virtual thread
2026-03-27 12:25 UTC "beikov (@beikov)" <[email protected]>
[3+ messages in thread]
[pgjdbc/pgjdbc] PR #4009: [#2325] Execute queries as pipelined when running on virtual thread
2026-03-26 07:45 UTC "beikov (@beikov)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #4009: [#2325] Execute queries as pipelined when running on virtual thread
2026-03-26 17:36 UTC "beikov (@beikov)" <[email protected]>
[2+ messages in thread]
[pgjdbc/pgjdbc] PR #4008: chore: use @vlsi/github-actions-random-matrix npm package
2026-03-25 08:42 UTC "vlsi (@vlsi)" <[email protected]>
[pgjdbc/pgjdbc] PR #4007: chore: use tag names for pinning github actions, pin ikalnytskyi/action-setup-postgres
2026-03-24 07:39 UTC "vlsi (@vlsi)" <[email protected]>
[pgjdbc/pgjdbc] PR #3996: fix: enable cursor-based fetching in extended protocol when transaction started via SQL command
2026-03-23 12:14 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3996: fix: enable cursor-based fetching in extended protocol when transaction started via SQL command
2026-03-23 15:03 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3996: fix: enable cursor-based fetching in extended protocol when transaction started via SQL command
2026-03-23 15:09 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3996: fix: enable cursor-based fetching in extended protocol when transaction started via SQL command
2026-03-23 15:12 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3996: fix: enable cursor-based fetching in extended protocol when transaction started via SQL command
2026-03-23 15:57 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3996: fix: enable cursor-based fetching in extended protocol when transaction started via SQL command
2026-03-23 16:00 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3996: fix: enable cursor-based fetching in extended protocol when transaction started via SQL command
2026-03-23 17:18 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3996: fix: enable cursor-based fetching in extended protocol when transaction started via SQL command
2026-03-24 07:06 UTC "vlsi (@vlsi)" <[email protected]>
[8+ messages in thread]
[pgjdbc/pgjdbc] PR #4006: test: add tests for QueryExecutor#getTransactionState
2026-03-24 07:04 UTC "vlsi (@vlsi)" <[email protected]>
[pgjdbc/pgjdbc] PR #4005: chore: bump errorprone to 2.48.0
2026-03-24 05:59 UTC "vlsi (@vlsi)" <[email protected]>
[pgjdbc/pgjdbc] PR #4004: fix(deps): update dependency org.roaringbitmap:roaringbitmap to v1.6.13
2026-03-23 21:18 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #4003: fix(deps): update dependency org.ow2.asm:asm-bom to v9.9.1
2026-03-23 21:18 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #4002: fix(deps): update dependency org.mockito:mockito-bom to v5.23.0
2026-03-23 18:28 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #4001: fix(deps): update dependency org.apache.bcel:bcel to v6.12.0
2026-03-23 18:28 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2022-10-20 19:12 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2022-10-20 19:13 UTC "gitguardian[bot] (bot) (@gitguardian[bot])" <noreply+gitguardian[bot]@github.com>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2022-10-20 20:45 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2022-10-22 10:52 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2023-01-06 16:18 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2023-01-06 16:23 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2023-06-06 13:43 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-01-16 19:41 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-04-18 06:50 UTC "androa (@androa)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-04-18 13:09 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-04-18 13:29 UTC "sehrope (@sehrope)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-12 19:49 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-12 19:52 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-12 21:17 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-13 07:38 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-13 07:47 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-13 07:47 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-13 07:48 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-13 07:49 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-13 07:57 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-13 08:00 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-13 15:47 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-13 15:53 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-14 18:41 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-14 19:07 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-14 19:23 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-15 06:25 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-15 06:29 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-15 06:30 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-15 18:50 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-15 18:57 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-15 19:13 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-15 19:14 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-18 21:44 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-22 08:13 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-22 08:21 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-27 09:12 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-28 08:38 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-28 11:38 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-28 12:47 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-31 13:15 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-05-31 13:28 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-06-04 06:31 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-06-04 07:16 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-06-07 06:35 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-09-09 08:14 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2024-09-09 10:59 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2025-03-18 14:46 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2025-06-20 13:27 UTC "mmand (@mmand)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2025-10-16 06:53 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2025-10-17 12:20 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2025-10-23 11:46 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2025-10-24 05:34 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2026-03-20 19:01 UTC "MarekUniq (@MarekUniq)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #2646: feat: improve libpq compatibility for URL parsing, environment variables, passfile, and property naming
2026-03-23 17:05 UTC "vlsi (@vlsi)" <[email protected]>
[55+ messages in thread]
[pgjdbc/pgjdbc] PR #4000: fix(deps): update dependency net.ltgt.errorprone:net.ltgt.errorprone.gradle.plugin to v4.4.0
2026-03-23 13:23 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3999: fix(deps): update dependency com.google.errorprone:error_prone_core to v2.48.0 - autoclosed
2026-03-23 13:23 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3998: fix(deps): update com.gradleup.nmcp to v1.4.4
2026-03-23 12:45 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3997: fix(deps): update checkerframework to v3.54.0
2026-03-23 12:45 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] issue #3993: fix Enable cursor-based bug, when start transaction by 'START TRANSAC'
2026-03-23 10:19 UTC "qinarmy-zoro (@qinarmy-zoro)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3993: fix Enable cursor-based bug, when start transaction by 'START TRANSAC'
2026-03-23 10:19 UTC "qinarmy-zoro (@qinarmy-zoro)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3993: fix Enable cursor-based bug, when start transaction by 'START TRANSAC'
2026-03-23 10:22 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3993: fix Enable cursor-based bug, when start transaction by 'START TRANSAC'
2026-03-23 10:26 UTC "qinarmy-zoro (@qinarmy-zoro)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3993: fix Enable cursor-based bug, when start transaction by 'START TRANSAC'
2026-03-23 10:35 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3993: fix Enable cursor-based bug, when start transaction by 'START TRANSAC'
2026-03-23 10:48 UTC "qinarmy-zoro (@qinarmy-zoro)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3993: fix Enable cursor-based bug, when start transaction by 'START TRANSAC'
2026-03-23 10:54 UTC "qinarmy-zoro (@qinarmy-zoro)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3993: fix Enable cursor-based bug, when start transaction by 'START TRANSAC'
2026-03-23 11:17 UTC "davecramer (@davecramer)" <[email protected]>
[8+ messages in thread]
[pgjdbc/pgjdbc] PR #3995: chore(deps): update release-drafter/release-drafter action to v6.4.0
2026-03-23 10:21 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[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