Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem: I would like to utilize some of the more advanced connection options avalible to as part of 'connect' in nwerver versions.
In particular I would like the ability to use SSL or GSSAPI. I believe support for these was added in psycopg-2.4.3 (current upstream is 2.5)
Version-Release number of selected component (if applicable): python-psycopg2-2.0.14-2.el6
How reproducible: always
Steps to Reproduce:
1. wish for SSL auth
2. wish for GSSAPI auth
3. find no way to do them in python-psycopg2
Actual results:
inability to do this auth
Expected results:
support for the same auth methods as postgresql.
Additional info:
http://initd.org/psycopg/http://initd.org/psycopg/docs/news.html
Thanks for the suggestion. If you want to increase chances for this package rebase, please raise your request through support channels ( https://www.redhat.com/support/process/production/#howto ) as update capacity is limited and prioritization is done based on the support cases.
As for rebasing request in order to have new features available in RHEL-6 -- there is already a new version of this package in python27 and python33 collections, which are parts of RHSCL 1.0. I'm not sure if this can solve your issues, but it should be mentioned here at least.
Rebase of python-psycopg2 package would be risky process which could break lot
of user's applications written to work exactly with
python-psycopg2-2.0.14-2.el6 version (there may be small nuances but even
these will complicate a work a lot).
As Honza said in comment #7, we now ship sufficiently new psycopg2 module
packaged in software collections (version 2.4.5), which may help in some
scenarios.
If this issue is critical or in any way time sensitive, please raise a ticket
through your regular Red Hat support channels to make certain it receives the
proper attention and prioritization to assure a timely resolution.
For information on how to contact the Red Hat production support team, please
visit:
https://www.redhat.com/support/process/production/#howto