Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

I've upgraded my JIRA Core to 8.0.2 and having locale issues

I've upgraded my JIRA Core to 8.0.2 from 7.x and it gave me PostgreSQL locale error.


Your postgres72 database is currently using an unsupported collation: en_US.UTF-8. You should change this to a supported collation:

  • C.UTF-8
  • C

First, I'm using PostgreSQL 9.6, not 7.2. Second I have to support UTF-8. But when I ask my computer for available locales; even it has C and POSIX, it does not have UTF-8 versions. BTW my OS is CentOS 7.

I'm trying to find a way to add C.UTF-8 to my OS but couldn't yet. Maybe you can help.



1 answer

Yeah. The postgres72 thing is an artifact from the old days. Don't let that send you in the wrong direction.

You do need to fix the data collation, though. You can have problems if it is wrong.  It's a relatively easy problem to fix, thankfully. This doc describes a method that involves exporting your data as XML, setting up a new postgres instance correctly and then importing the XML data back in. Assuming you have a relatively small amount of data, this is a sensible method and the least risky way to solve the problem. There are also a number of ways to correct this manually in the database. (google for "postgres alter table collation") As always, test this first in a non-production environment, validate that things work properly and then follow the same procedure in production.  

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

309 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you