-
Suggestion
-
Resolution: Fixed
-
256
-
3
-
-
PostgreSQL 11 has been released, but is not a Supported platform.
Requesting PostgreSQL 11 support.
- blocks
-
- Closed
- is related to
-
- Closed
- relates to
-
- Closed
-
![[JIRA Server (Bulldog)] Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.](https://bulldog.internal.atlassian.com/images/icons/issuetypes/epic.svg "[JIRA Server (Bulldog)] Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.")
SPLAT-89
You do not have permission to view this issue
- mentioned in
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
- resolves
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRASERVER-68578] JIRA support for Postgres 11
Postgres is backwards compatible for at least two versions. We updated all JIRA/Confluence Services (7.13 - 8.7) in our QA Stage to Postgres12 and they run like the good old Mercedes Benz 
Never had issues with the customer support like "closing ticket, unsupported database...Have a nice day"
Yeah - maybe Atlassian cant help me in case of any DB related issues - but i dont mind.
I think it's obvious - but I have to suggest it anyways in case it isn't: Atlassian, if you are encountering problems with using new versions of PostgreSQL, can you please review why this would be, so that it isn't such a problem?
I've been assuming all along that there is almost nothing to backport with regard to "We're also working on backporting PostgreSQL 10 to the Enterprise Release stream." beyond perhaps updating PostgreSQL JDBC and adding test infrastructure. But, if there really is something that needs to change in Jira source code, then I would wonder why that is. Reducing technical debt should mean eliminating such things from being a problem in the first place.
... or worse. I can't remember which Atlassian product it was, but one of them added a check and using the newer PostgreSQL version appeared to work fine, but then later failed with a patch update as it refused to start. Luckily for me - it was a home system that I use to play with Atlassian products before installing them at work, and the reason I was updating was in preparation for upgrade that did support later version, but still, that was a bit of a surprise to have a working system fail only because of a new check. But, definitely be wary of this, and definitely test before deploying to production. 
Nice - the official supported notice is important to get immediate support from Atlassian. If you are running a not supported DB backend or version which is not yet officially supported a ticket might be taking more time or even be closed.
PostgreSQL 11 support is now available in Jira 8.7 along with user anonymization for GDPR compliance and OpenID Connect integration (Data Center). You can read the release notes and download the latest version here.
Support for PostgreSQL 10 for Jira Software, Jira Service Desk and Portfolio for Jira has been available since version 8.6 / 4.6. We're also working on backporting PostgreSQL 10 to the Enterprise Release stream. I will be posting updates about the backport on JRASERVER-65910.
Katarzyna Derenda
Product Manager, Jira Server and Data Center
Also waiting for Jira 8.7 because the latest debian OS buster also uses PostgreSQL 11 as their default postgres database.
cwrinn Postgres 11 will not be officially supported in the 8.5.x Enterprise Release stream, only Postgres 10 will. Postgres 11 will be supported in the next Enterprise Release and in 8.7.0.
However, starting from 8.5.4 release, you will be able to use Postgres 11 with Jira, but there will be a warning in the admin troubleshooting page for the DVCS plugin. Everything else should work just fine, however it's not officially supported.
Will support for Postgres 11 be backported to the Enterprise Release of 8.5?
I like the car reference ... but that you might run into problems with support tickets is the only downside I have read about when not fulfilling the requirements of the supported platforms section.
But it is nice to also get feedback from other server users that can confirm using newer versions does not cause any problems. Since we are also developing a web application with multiple possible SQL backends I know about the hassle with migration scripts and newer versions of database engines.