RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1687598 - Consider upgrading postgres-jdbc shipped with RHEL to 42.2.5
Summary: Consider upgrading postgres-jdbc shipped with RHEL to 42.2.5
Keywords:
Status: CLOSED DUPLICATE of bug 1583944
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: postgresql-jdbc
Version: 7.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Pavel Raiskup
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-11 20:42 UTC by Dustin Kut Moy Cheung
Modified: 2019-03-14 08:32 UTC (History)
6 users (show)

Fixed In Version: postgresql-jdbc-9.2.1002-6.el7_5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-12 05:46:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1547424 0 high CLOSED postgresql-jdbc not compatible with PostgreSQL 9.6 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1572682 0 high CLOSED postgresql-jdbc not compatible with PostgreSQL 9.6 [rhel-7.5.z] 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1583944 0 unspecified CLOSED postgresql-jdbc 9.2 is not compatible with postgresql 10 2021-02-22 00:41:40 UTC

Description Dustin Kut Moy Cheung 2019-03-11 20:42:13 UTC
Description of problem:


Version-Release number of selected component (if applicable): 9.2


How reproducible: Always


Steps to Reproduce:
1. Use postgres-jdbc92 to connect to a Postgres 10 server

Actual results:
- Failed to connect due to incompatibilities


Expected results:
- It should be able to connect to a Postgres 10 server

Additional info:
- We are using the RH-SSO 7.3 Docker image. We're told that the Postgres JDBC driver used in that image is inherited from the RHEL rpm. Therefore we'd like to get the Postgres JDBC driver shipped with RHEL to be upgraded to the latest jdbc driver since the latest one should be backwards compatible to older versions of Postgres. We want the upgrade because we'd like the RH-SSO 7.3 Docker image to be able to talk to a Postgres 10 server out of the box without any further modifications.

Comment 2 Pavel Raiskup 2019-03-12 05:46:33 UTC
Thanks for the report Dustin, you did not specify the version
of the package you are currently using.  Since this should be already
fixed in RHEL 7, I'm closing this bug.  Please update your package,
and if there are still some compatibility problems, reopen.

*** This bug has been marked as a duplicate of bug 1583944 ***

Comment 3 Martin Kanis 2019-03-14 08:15:11 UTC
Version of the package is postgresql-jdbc-9.2.1002-6.el7_5 where the problem should be fixed according "Fixed In Version" field but as Dustin mentioned it's not.

Comment 4 Pavel Raiskup 2019-03-14 08:32:51 UTC
Well, Dustin wrote that jdbc isn't able to talk to PostgreSQL 10,
which should be fixed.  Can we have a reproducer please?


Note You need to log in before you can comment on or make changes to this bug.