invalid value for parameter "TimeZone": "US/Pacific-new"

Yuriy Grinberg July 8, 2018

Jira 7 fails to connect to Postgresql 10

throws tihs:

org.postgresql.util.PSQLException: FATAL: invalid value for parameter "TimeZone": "US/Pacific-New"

I know the latest postgres is not in the list of supported databases

is there a workaround ?

1 answer

0 votes
Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 9, 2018

Yuriy,

Indeed Jira 7 won't work properly with PostgreSQL 10 and the workaround is to revert to a supported version: 9.2, 9.3, or 9.4

You may also want to try a different timezone in case the one you're using isn't recognized:

A full time zone name, for example America/New_York. The recognized time zone names are listed in the pg_timezone_names view (see Section 51.90). PostgreSQL uses the widely-used IANA time zone data for this purpose, so the same time zone names are also recognized by much other software.

Regards,

Shannon

Yuriy Grinberg July 9, 2018

Hi Shannon,

Thank you for a quick reply.

 

I would prefer to use one of the supported time zones and go with pgsql 10

How can I specify the time zone?

Is it somewhere in jira configuration ?

 

thank you

Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 10, 2018

Hi Yuriy,

To be clear, there is a good chance this won't solve your issue, since Postgres 10 isn't supported by Jira at this time.

Have a look at my colleague's response below:

You will want to get in touch with your database admin if you have any issues getting that updated.

If you continue to encounter problems I highly recommend you migrate to a supported database version. There are no guarantees when running Jira off an unsupported database.

Shannon

Yuriy Grinberg July 10, 2018

It is sad when support team puts up a "not officially supported" barricade while the answer is rather simple.

older linux/jvm supplies the timezone that new postgres no longer recognizes

"-Duser.timezone America/Los_Angeles" is all it takes, thank god for google

It would have been so nice if you gave an actual answer.

It would be quite surprising if postgres actually dropped a fundamental SQL feature in v10 to make it unusable for jira.

 

all in all a rather unsatisfactory experience

i've been using jira for close to 15 years now, brought it to several companies

and now this...

Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 11, 2018

Hi Yuriy,

I'm happy to hear the suggested change to go to a supported timezone fixed the issue! I wasn't personally aware of the issue with old versions of Linux and Postgres. This is something that we will surely be able to document once Postgres 10 is officially supported.

If you do run into any other issues using Postgres 10, please feel free to submit them as feedback and we can include a fix for it when a version of Jira is released that supports it.

Take care, and have a pleasant rest of your week!

Regards,

Shannon

Suggest an answer

Log in or Sign up to answer