• 10
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Confluence does not support Postgres 9.6, and will throw error messages like the following:

      org.postgresql.util.PSQLException: ERROR: column am.amcanorder does not exist
      
      

      Upgrading the Postgres Driver to the newest version seems to resolve the problem, however Atlassian Support will not be able to provide support for this configuration until this improvement is implemented in a future version.

      Upgrade the Postgres Driver
      1. Shut down Confluence
      2. Copy confluence-install/confluence/WEB-INF/lib/postgresql-9.x-xxxx.jdbc4.jar to a safe location as a backup, and then delete the file.
      3. From the Postgres Website, download the most recent driver and copy it to the same location
        • Despite its name, the JDBC 9.4 driver is compatible with Postgres 9.6
      4. Start Confluence again

      Notes

      This is documented here

            [CONFSERVER-44216] Support Postgres 9.6

            AregVrtanesyan added a comment - - edited

            Confluence documentation states that it is supporting 9.6 from v6.3 and up

            https://confluence.atlassian.com/conf63/supported-platforms-929730053.html

            We are on Enterprise Release 6.6 and all ok.

            AregVrtanesyan added a comment - - edited Confluence documentation states that it is supporting 9.6 from v6.3 and up https://confluence.atlassian.com/conf63/supported-platforms-929730053.html We are on Enterprise Release 6.6 and all ok.

            @Brett 

            /opt/atlassian/jira/lib

            Had the same trouble finding it.

            Mike Monette added a comment - @Brett  /opt/atlassian/jira/lib Had the same trouble finding it.

            A fix for this issue is now available for Confluence Server customers.
            Upgrade now or check out the Release Notes to see what other issues are resolved.

            Jenny (Inactive) added a comment - A fix for this issue is now available for Confluence Server customers. Upgrade now or check out the Release Notes to see what other issues are resolved.

            Eric - this is the issue they are writing about.

            Jacek Pliszka added a comment - Eric - this is the issue they are writing about.

            The Confluence Supported Platforms page says that "9.6 is not supported and has known issues". This is not true, there are no "known" issues. Please adjust the text to read "9.6 is not supported yet".

            Deleted Account (Inactive) added a comment - The Confluence Supported Platforms page says that "9.6 is not supported and has known issues" . This is not true, there are no "known" issues. Please adjust the text to read "9.6 is not supported yet" .

            markmielke added a comment -

            Make sure you are using an up-to-date postgresql-jdbc version: https://jdbc.postgresql.org/

            One of my test instances has PostgreSQL JDBC 42.0.0 version with JIRA 7.3.3 on PostgreSQL 9.6.2. No problems encountered so far. If you wanted to be a little cautious, you might choose to stay on postgresql-jdbc 9.4.1212. They jumped the version from 9.4 to 42.0 to avoid implying a line up requirement between PostgreSQL JDBC and the PostgreSQL. The 9.4.1212 should work fine on 9.6, but people may have been making too much of the "9.4". However, when they leapt to 42.0, they also included some additional changes that could introduce a small amount of new risk.

             

            markmielke added a comment - Make sure you are using an up-to-date postgresql-jdbc version: https://jdbc.postgresql.org/ One of my test instances has PostgreSQL JDBC 42.0.0 version with JIRA 7.3.3 on PostgreSQL 9.6.2. No problems encountered so far. If you wanted to be a little cautious, you might choose to stay on postgresql-jdbc 9.4.1212. They jumped the version from 9.4 to 42.0 to avoid implying a line up requirement between PostgreSQL JDBC and the PostgreSQL. The 9.4.1212 should work fine on 9.6, but people may have been making too much of the "9.4". However, when they leapt to 42.0, they also included some additional changes that could introduce a small amount of new risk.  

            Basically, can't create any new anything (task, issue, project, user, etc.) in JIRA.

            Confluence doesn't allow me to create/update.

            Caused by: org.postgresql.util.PSQLException: ERROR: column am.amcanorder does not exist

            I uninstalled PostgreSQL 9.6.2 and Confluence, and re-installed 9.4.11 and Confluence.

            I'll switch to the 9.6.2 instance and attach the logs.

             

            Patrick Kyne added a comment - Basically, can't create any new anything (task, issue, project, user, etc.) in JIRA. Confluence doesn't allow me to create/update. Caused by: org.postgresql.util.PSQLException: ERROR: column am.amcanorder does not exist I uninstalled PostgreSQL 9.6.2 and Confluence, and re-installed 9.4.11 and Confluence. I'll switch to the 9.6.2 instance and attach the logs.  

            @patrick what is the error that you observed when upgrading to 9.6?

            Deleted Account (Inactive) added a comment - @patrick what is the error that you observed when upgrading to 9.6?

            This doesn't appear to work with JIRA -Software 7.3 or JIRA Core 7.3.

            I hope the JIRA team and the Confluence team can get this fixed soon, as delaying PostgreSQL upgrade to 9.6.x is getting harder to justify.

            Perhaps 9.6 will require a schema change from the current Postgresql72 version.

            Patrick Kyne added a comment - This doesn't appear to work with JIRA -Software 7.3 or JIRA Core 7.3. I hope the JIRA team and the Confluence team can get this fixed soon, as delaying PostgreSQL upgrade to 9.6.x is getting harder to justify. Perhaps 9.6 will require a schema change from the current Postgresql72 version.

            ericshane1517580246, we have not setup the build automation to test against 9.6, so nothing passing, nor nothing failing. My statement 'appears to work' is based on customers choosing to run this and not reporting issues.

            Adam Barnes (Inactive) added a comment - ericshane1517580246 , we have not setup the build automation to test against 9.6, so nothing passing, nor nothing failing. My statement 'appears to work' is based on customers choosing to run this and not reporting issues.

              ttranminh Tam Tran
              dnorton@atlassian.com Dave Norton
              Votes:
              54 Vote for this issue
              Watchers:
              58 Start watching this issue

                Created:
                Updated:
                Resolved: