pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feed[pgjdbc/pgjdbc] PR #3520: fix(deps): update dependency checkstyle to v10.21.3
2025-02-10 09:26 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3519: chore(deps): update plugin org.jetbrains.kotlin.jvm to v2.1.10
2025-02-10 05:42 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3518: chore(deps): update plugin me.champeau.jmh to v0.7.3
2025-02-10 05:42 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3517: chore(deps): update dependency gradle to v8.12.1
2025-02-10 00:55 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3516: chore(deps): update codecov/codecov-action digest to 5efa07b
2025-02-10 00:50 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] issue #3433: Same timestamps, but different values when saved (executeUpdate) to database
2024-11-07 15:15 UTC "anaconda875 (@anaconda875)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3433: Same timestamps, but different values when saved (executeUpdate) to database
2024-11-07 15:26 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3433: Same timestamps, but different values when saved (executeUpdate) to database
2024-11-07 16:21 UTC "anaconda875 (@anaconda875)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3433: Same timestamps, but different values when saved (executeUpdate) to database
2024-11-07 16:24 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3433: Same timestamps, but different values when saved (executeUpdate) to database
2024-11-07 16:25 UTC "anaconda875 (@anaconda875)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3433: Same timestamps, but different values when saved (executeUpdate) to database
2024-11-07 19:30 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3433: Same timestamps, but different values when saved (executeUpdate) to database
2024-11-08 01:42 UTC "anaconda875 (@anaconda875)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3433: Same timestamps, but different values when saved (executeUpdate) to database
2024-11-08 06:13 UTC "anaconda875 (@anaconda875)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3433: Same timestamps, but different values when saved (executeUpdate) to database
2024-11-09 04:47 UTC "anaconda875 (@anaconda875)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3433: Same timestamps, but different values when saved (executeUpdate) to database
2025-02-07 16:14 UTC "anaconda875 (@anaconda875)" <[email protected]>
[10+ messages in thread]
[pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-02 19:40 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-02 19:51 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-02 20:23 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-02 20:40 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-02 20:44 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-02 20:52 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-02 21:20 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-03 15:34 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-03 15:37 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-03 15:38 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-03 15:41 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-03 21:19 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-03 21:24 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-04 07:10 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-04 09:41 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-04 12:51 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-04 12:58 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-04 13:14 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-04 14:47 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-04 19:12 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-04 19:18 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-04 19:28 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-04 19:40 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-04 20:12 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-07 09:10 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
2025-02-07 09:39 UTC "vlsi (@vlsi)" <[email protected]>
[26+ messages in thread]
[pgjdbc/pgjdbc] issue #3467: DatabaseMetaData.getIndexInfo() doesn't return "REMARKS" property
2024-12-22 17:32 UTC "ldhasson (@ldhasson)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3467: DatabaseMetaData.getIndexInfo() doesn't return "REMARKS" property
2024-12-30 03:57 UTC "Shanayshah44 (@Shanayshah44)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3467: DatabaseMetaData.getIndexInfo() doesn't return "REMARKS" property
2024-12-30 04:09 UTC "ldhasson (@ldhasson)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3467: DatabaseMetaData.getIndexInfo() doesn't return "REMARKS" property
2024-12-30 04:12 UTC "Shanayshah44 (@Shanayshah44)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3467: DatabaseMetaData.getIndexInfo() doesn't return "REMARKS" property
2024-12-30 05:12 UTC "ldhasson (@ldhasson)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3467: DatabaseMetaData.getIndexInfo() doesn't return "REMARKS" property
2024-12-30 10:23 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3467: DatabaseMetaData.getIndexInfo() doesn't return "REMARKS" property
2024-12-30 14:21 UTC "ldhasson (@ldhasson)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3467: DatabaseMetaData.getIndexInfo() doesn't return "REMARKS" property
2024-12-30 14:36 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3467: DatabaseMetaData.getIndexInfo() doesn't return "REMARKS" property
2025-02-06 12:20 UTC "raminorujov (@raminorujov)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3467: DatabaseMetaData.getIndexInfo() doesn't return "REMARKS" property
2025-02-06 14:04 UTC "raminorujov (@raminorujov)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3467: DatabaseMetaData.getIndexInfo() doesn't return "REMARKS" property
2025-02-06 14:11 UTC "ldhasson (@ldhasson)" <[email protected]>
[11+ messages in thread]
[pgjdbc/pgjdbc] PR #3513: feat: enhanced DatabaseMetadata.getIndexInfo() method, added index comment as REMARKS property
2025-02-06 11:08 UTC "raminorujov (@raminorujov)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3513: feat: enhanced DatabaseMetadata.getIndexInfo() method, added index comment as REMARKS property
2025-02-06 11:11 UTC "raminorujov (@raminorujov)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3513: feat: enhanced DatabaseMetadata.getIndexInfo() method, added index comment as REMARKS property
2025-02-06 11:32 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3513: feat: enhanced DatabaseMetadata.getIndexInfo() method, added index comment as REMARKS property
2025-02-06 12:43 UTC "vlsi (@vlsi)" <[email protected]>
[4+ messages in thread]
[pgjdbc/pgjdbc] issue #1390: LocalDateTime has invalid string serialization
2019-01-18 16:58 UTC "kdubb (@kdubb)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #1390: LocalDateTime has invalid string serialization
2019-01-18 17:32 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #1390: LocalDateTime has invalid string serialization
2019-01-18 17:34 UTC "kdubb (@kdubb)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #1390: LocalDateTime has invalid string serialization
2019-01-18 17:50 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #1390: LocalDateTime has invalid string serialization
2019-01-18 17:57 UTC "kdubb (@kdubb)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #1390: LocalDateTime has invalid string serialization
2019-03-10 21:16 UTC "mpilone (@mpilone)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #1390: LocalDateTime has invalid string serialization
2020-09-24 23:04 UTC "alexbishop1 (@alexbishop1)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #1390: LocalDateTime has invalid string serialization
2020-09-25 08:20 UTC "findepi (@findepi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #1390: LocalDateTime has invalid string serialization
2020-09-25 10:37 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #1390: LocalDateTime has invalid string serialization
2025-02-06 11:39 UTC "davecramer (@davecramer)" <[email protected]>
[10+ messages in thread]
[pgjdbc/pgjdbc] PR #3512: feat: enhanced DatabaseMetadata added index comment as REMARKS
2025-02-06 09:42 UTC "raminorujov (@raminorujov)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3512: feat: enhanced DatabaseMetadata added index comment as REMARKS
2025-02-06 09:46 UTC "raminorujov (@raminorujov)" <[email protected]>
[2+ messages in thread]
[pgjdbc/pgjdbc] issue #3507: problem using 42.7.5 with jOOQ: llegalArgumentException: Field "key_seq" is not contained in row type
2025-02-03 07:03 UTC "FrankHossfeld (@FrankHossfeld)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3507: problem using 42.7.5 with jOOQ: llegalArgumentException: Field "key_seq" is not contained in row type
2025-02-03 07:05 UTC "FrankHossfeld (@FrankHossfeld)" <[email protected]>
[2+ messages in thread]
Re: [pgjdbc/pgjdbc] PR #3280: WIP Asynchronous ResultSetHandler
2025-02-02 20:25 UTC "davecramer (@davecramer)" <[email protected]>
Re: [pgjdbc/pgjdbc] PR #3280: WIP Asynchronous ResultSetHandler
2025-02-02 19:42 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
[pgjdbc/pgjdbc] issue #3490: Clarify startup parameter selection since Version 12 for extra_float_digits
2025-01-22 00:52 UTC "ecki (@ecki)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3490: Clarify startup parameter selection since Version 12 for extra_float_digits
2025-01-22 01:23 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3490: Clarify startup parameter selection since Version 12 for extra_float_digits
2025-01-22 07:07 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3490: Clarify startup parameter selection since Version 12 for extra_float_digits
2025-02-02 19:07 UTC "ecki (@ecki)" <[email protected]>
[4+ messages in thread]
[pgjdbc/pgjdbc] issue #3435: it's better to just switch to NIO and SocketChannel?
2024-11-08 03:03 UTC "chenzhenyang (@chenzhenyang)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3435: it's better to just switch to NIO and SocketChannel?
2024-11-08 09:54 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3435: it's better to just switch to NIO and SocketChannel?
2025-01-31 08:10 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3435: it's better to just switch to NIO and SocketChannel?
2025-01-31 13:25 UTC "davecramer (@davecramer)" <[email protected]>
[4+ messages in thread]
[pgjdbc/pgjdbc] PR #3503: Nit: correct message in main.yml test action
2025-01-30 23:22 UTC "ecki (@ecki)" <[email protected]>
[pgjdbc/pgjdbc] PR #3257: test: add CI testing against PostgreSQL HEAD
2024-05-21 19:39 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3257: test: add GitHub CI testing with PostgreSQL 15 and HEAD
2024-05-21 20:43 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3257: test: add GitHub CI testing with PostgreSQL 15 and HEAD
2024-05-21 20:48 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3257: test: add GitHub CI testing with PostgreSQL 15 and HEAD
2024-05-21 20:54 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3257: test: add GitHub CI testing with PostgreSQL 15 and HEAD
2024-05-21 20:59 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3257: test: add GitHub CI testing with PostgreSQL 15 and HEAD
2024-05-22 09:51 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3257: test: add GitHub CI testing with PostgreSQL 15 and HEAD
2024-05-22 12:45 UTC "sehrope (@sehrope)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3257: test: add GitHub CI testing with PostgreSQL 15 and HEAD
2025-01-28 13:23 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3257: test: add GitHub CI testing with PostgreSQL 15 and HEAD
2025-01-28 13:28 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3257: test: add GitHub CI testing with PostgreSQL 15 and HEAD
2025-01-28 13:55 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3257: test: add GitHub CI testing with PostgreSQL 15 and HEAD
2025-01-28 13:57 UTC "vlsi (@vlsi)" <[email protected]>
[11+ messages in thread]
[pgjdbc/pgjdbc] PR #3502: chore: use import instead of require to support modern NodeJS
2025-01-28 11:32 UTC "vlsi (@vlsi)" <[email protected]>
[pgjdbc/pgjdbc] PR #3501: chore: use PostgreSQL 17 rather than 17rc1 for CI tests
2025-01-28 09:53 UTC "vlsi (@vlsi)" <[email protected]>
[pgjdbc/pgjdbc] PR #3492: fix: ArrayIndexOutOfBounds when write big object into GSS enabled connection
2025-01-22 08:33 UTC "Sasasu (@Sasasu)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3492: fix: ArrayIndexOutOfBounds when write big object into GSS enabled connection
2025-01-22 09:02 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3492: fix: ArrayIndexOutOfBounds when write big object into GSS enabled connection
2025-01-22 09:03 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3492: fix: ArrayIndexOutOfBounds when write big object into GSS enabled connection
2025-01-22 09:03 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3492: fix: ArrayIndexOutOfBounds when write big object into GSS enabled connection
2025-01-22 09:16 UTC "Sasasu (@Sasasu)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3492: fix: ArrayIndexOutOfBounds when write big object into GSS enabled connection
2025-01-22 09:35 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3492: fix: ArrayIndexOutOfBounds when write big object into GSS enabled connection
2025-01-23 09:07 UTC "Sasasu (@Sasasu)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3492: fix: ArrayIndexOutOfBounds when write big object into GSS enabled connection
2025-01-23 10:34 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3492: fix: ArrayIndexOutOfBounds when write big object into GSS enabled connection
2025-01-24 09:16 UTC "Sasasu (@Sasasu)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3492: fix: ArrayIndexOutOfBounds when write big object into GSS enabled connection
2025-01-24 09:25 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3492: fix: ArrayIndexOutOfBounds when write big object into GSS enabled connection
2025-01-24 09:26 UTC "Sasasu (@Sasasu)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3492: fix: ArrayIndexOutOfBounds when write big object into GSS enabled connection
2025-01-27 14:39 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3492: fix: ArrayIndexOutOfBounds when write big object into GSS enabled connection
2025-01-28 08:10 UTC "vlsi (@vlsi)" <[email protected]>
[13+ messages in thread]
[pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-17 09:08 UTC "james-johnston-thumbtack (@james-johnston-thumbtack)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-17 09:21 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-17 09:36 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-17 09:39 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-17 09:54 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-17 10:43 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-17 10:45 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-17 11:00 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-17 11:11 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-17 19:01 UTC "james-johnston-thumbtack (@james-johnston-thumbtack)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-19 09:08 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-20 15:08 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-21 00:41 UTC "james-johnston-thumbtack (@james-johnston-thumbtack)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-21 15:17 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-21 20:01 UTC "james-johnston-thumbtack (@james-johnston-thumbtack)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-21 20:04 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-21 20:13 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-27 12:31 UTC "Chris-SP365 (@Chris-SP365)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-27 20:26 UTC "james-johnston-thumbtack (@james-johnston-thumbtack)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
2025-01-28 06:34 UTC "Chris-SP365 (@Chris-SP365)" <[email protected]>
[20+ messages in thread]
[pgjdbc/pgjdbc] PR #3500: fix: ArrayIndexOutOfBounds when write big object into GSS enabled connection, make GSSInputStream robust in face of streams that produce incomplete reads
2025-01-27 14:34 UTC "vlsi (@vlsi)" <[email protected]>
[pgjdbc/pgjdbc] PR #3493: chore: add ErrorProne verification to catch bugs ealier
2025-01-22 10:03 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3493: chore: add ErrorProne verification to catch bugs ealier
2025-01-22 13:52 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3493: chore: add ErrorProne verification to catch bugs ealier
2025-01-24 13:37 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3493: chore: add ErrorProne verification to catch bugs ealier
2025-01-24 14:02 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3493: chore: add ErrorProne verification to catch bugs ealier
2025-01-24 14:53 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3493: chore: add ErrorProne verification to catch bugs ealier
2025-01-25 12:05 UTC "davecramer (@davecramer)" <[email protected]>
[6+ messages in thread]
[pgjdbc/pgjdbc] PR #3451: Support default GSS credentials in the Java Postgres client
2024-11-21 18:14 UTC "nrhall (@nrhall)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3451: Support default GSS credentials in the Java Postgres client
2024-11-22 17:37 UTC "nrhall (@nrhall)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3451: Support default GSS credentials in the Java Postgres client
2025-01-21 12:37 UTC "ecki (@ecki)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3451: Support default GSS credentials in the Java Postgres client
2025-01-21 12:40 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3451: Support default GSS credentials in the Java Postgres client
2025-01-22 01:45 UTC "ecki (@ecki)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3451: Support default GSS credentials in the Java Postgres client
2025-01-24 10:59 UTC "nrhall (@nrhall)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3451: Support default GSS credentials in the Java Postgres client
2025-01-24 11:18 UTC "nrhall (@nrhall)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3451: Support default GSS credentials in the Java Postgres client
2025-01-24 11:31 UTC "nrhall (@nrhall)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3451: Support default GSS credentials in the Java Postgres client
2025-01-24 11:42 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3451: Support default GSS credentials in the Java Postgres client
2025-01-24 11:50 UTC "nrhall (@nrhall)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3451: Support default GSS credentials in the Java Postgres client
2025-01-24 11:51 UTC "nrhall (@nrhall)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3451: Support default GSS credentials in the Java Postgres client
2025-01-24 11:53 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3451: Support default GSS credentials in the Java Postgres client
2025-01-24 12:18 UTC "nrhall (@nrhall)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3451: Support default GSS credentials in the Java Postgres client
2025-01-24 14:43 UTC "ecki (@ecki)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3451: Support default GSS credentials in the Java Postgres client
2025-01-24 15:41 UTC "nrhall (@nrhall)" <[email protected]>
[15+ 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