Red Hat Bugzilla – Bug 1106547
[RFE][Tracker]Support Postgresql 9.5
Last modified: 2018-05-15 13:38:12 EDT
Description of problem: Postgres <= 9.2 has a limitation where non-key-field row updates block foreign key checks (this is the root cause for, e.g., bug 1077715). This BZ is filed to track upgrading RHEVM's database to 9.3 (or higher) in order to prevent such bugs in the future, and allow creating foreign keys in such situations. Version-Release number of selected component (if applicable): 3.5.0 How reproducible: 100% Steps to Reproduce: 1. echo "select version()" | psql -U engine -d engine 2. 3. Actual results: Current postgres version is 8.4: """ version ------------------------------------------------------------------------------------------------------------------ PostgreSQL 8.4.20 on x86_64-redhat-linux-gnu, compiled by GCC gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4), 64-bit (1 row) """ Expected results: Postgres 9.3 or above. Additional info: See http://www.postgresql.org/docs/9.3/static/release-9-3.html, specifically secion 5.3.1.1 for details on the locking issue.
Moving to RHEV-M Future, as RHEL7 won't contain a postgres version higher than 9.2.
We still don't have any d/s build to test. Please move to ON_QA after proper build first created.
Engine 4.2 is installed/upgraded with 9.5 postgres - rh-postgresql95 from software collections. It's installable and connectable. All issues will be reported as separate bugs. verified in ovirt-engine-4.2.0-0.4.master.el7.noarch
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [No external trackers attached] For more info please contact: rhv-devops@redhat.com
INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [No external trackers attached] For more info please contact: rhv-devops@redhat.com
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:1488