Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Properly set cancel socket timeout like https://github.com/pgjdbc/pgjdbc/pull/2044 #77

Closed
RealTYPICAL opened this issue Dec 28, 2022 · 2 comments

Comments

@RealTYPICAL
Copy link

Driver version

2.0.0.3

Redshift version

PostgreSQL 8.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3), Redshift 1.0.44903

Client Operating System

UBI8

JAVA/JVM version

openjdk version "17.0.5" 2022-10-18

Table schema

N/A

Problem description

pgjdbc/pgjdbc#2044
The file found here: pgjdbc/pgjdbc@40b429e#diff-fb626514a44e1fd93551464de0ba369def2b0513a7232ce12d9c3040ea98d211
contains a fix for timeouts which the redshift driver does not have. Not having this fix can cause cancel() to hang. Is it possible to include the PG fix in the redshift driver codebase?

  1. Socket timeout should be handled properly.
  2. cancel() can hang infinitely.
  3. Error message/stack trace:
  4. Any other details that can be helpful:

JDBC trace logs

Reproduction code

@bhvkshah
Copy link
Contributor

Thank you for opening an issue. We will look into this and post here when we have an update.

@bhvkshah
Copy link
Contributor

bhvkshah commented Jan 18, 2023

Thank you for contributing to the Redshift JDBC 2.x Driver. The fix for the issue above will be in version 2.1.0.11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants