Bug 794457 (JBEPP-1497) - support PostgreSQL 8.4.9 in EPP 5.2.x
Summary: support PostgreSQL 8.4.9 in EPP 5.2.x
Keywords:
Status: CLOSED WONTFIX
Alias: JBEPP-1497
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Requirements
Version: 5.2.0.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.x
Assignee: Thomas Heute
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-01 20:11 UTC by Gary Hu
Modified: 2018-11-28 21:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-26 07:55:46 UTC
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-1497 0 Major Closed support PostgreSQL 8.4.9 in EPP 5.2.x 2012-12-10 19:03:45 UTC

Description Gary Hu 2012-02-01 20:11:01 UTC
Help Desk Ticket Reference: https://na7.salesforce.com/500A000000918bo
project_key: JBEPP

We've got a support ticket that request supporting PostgreSQL 8.4.9 and JDBC4 Postgresql Driver 8.4-703 in EPP 5.2.

"I am setting up an EPP solution bound to openLDAP for a customer (star alliance).

For security reasons the host provider prefers to user PostgreSQL version 8.4.9. Is there a way to certify / provide support for EPP 5.2 with PostgreSQL 8.4.9 (JDBC4 Postgresql Driver, Version 8.4-703) ?"

Can you review this feature request and decide if we can accept it?

Comment 1 Martin Weiler 2012-04-13 09:44:31 UTC
See:  http://www.postgresql.org/support/versioning/

Version	Current minor	Supported	First release date	EOL date
9.1	9.1.3	        Yes	        September 2011	        September 2016
9.0	9.0.7	        Yes	        September 2010	        September 2015
8.4	8.4.11	        Yes	        July 2009	        July 2014
8.3	8.3.18	        Yes	        February 2008	        February 2013
8.2	8.2.23	        No	        December 2006	        December 2011

EPP 5.2.0 is certified with PostgreSQL 8.2 and 8.3, the former already being EOL'd, and the latter in the last year of support. We need to certify on newer PostgreSQL versions.


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