We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-57749

Update health check with correct encoding requirements for Windows users on installation with PostgreSQL

      Problem Definition

      When upgrading Confluence to 6.14 or later, admins see the following message that English_United States.1252 is not UTF-8

      This is a false warning and can be ignored, provided the client encoding is set correctly.

      Background

      I've had several users on Community reach out to me regarding this confusion, for example:

      Until September 2019, the Database Setup for Postgresql doc specified that:

      Collation must also be set to utf8. Other collations, such as "C", are known to cause issues with Confluence.

      This is clear to Linux users, but for Windows users, their options might look like the following:

      • C
      • POSIX
      • English_United States.1252

      During setup of the database in Windows, users are to select a locale, and are presented with the following selections:

      Expected behavior

      Confluence health check does not give the false warning when using .1252 collations

      Suggested Solution

      We should update the health check to accept the Windows equivalent of UTF-8.

      Notes

      According to Postgres:

      UTF-8 encoding can be used with any locale.

      In addition, I reviewed this blog post, Locale in Windows, and it appears that you should be able to use English_United States.1252.

      Although I believe this is addressed with the following line:

      Choose the locale that best matches your geographic location.

        1. Capture.JPG
          Capture.JPG
          70 kB
        2. image.png
          image.png
          12 kB

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Confluence Data Center'
            1. Confluence Data Center
            2. CONFSERVER-57749

            Update health check with correct encoding requirements for Windows users on installation with PostgreSQL

                Problem Definition

                When upgrading Confluence to 6.14 or later, admins see the following message that English_United States.1252 is not UTF-8

                This is a false warning and can be ignored, provided the client encoding is set correctly.

                Background

                I've had several users on Community reach out to me regarding this confusion, for example:

                Until September 2019, the Database Setup for Postgresql doc specified that:

                Collation must also be set to utf8. Other collations, such as "C", are known to cause issues with Confluence.

                This is clear to Linux users, but for Windows users, their options might look like the following:

                • C
                • POSIX
                • English_United States.1252

                During setup of the database in Windows, users are to select a locale, and are presented with the following selections:

                Expected behavior

                Confluence health check does not give the false warning when using .1252 collations

                Suggested Solution

                We should update the health check to accept the Windows equivalent of UTF-8.

                Notes

                According to Postgres:

                UTF-8 encoding can be used with any locale.

                In addition, I reviewed this blog post, Locale in Windows, and it appears that you should be able to use English_United States.1252.

                Although I believe this is addressed with the following line:

                Choose the locale that best matches your geographic location.

                  1. Capture.JPG
                    Capture.JPG
                    70 kB
                  2. image.png
                    image.png
                    12 kB

                        jmoynihan Jamie (Inactive)
                        smackie@atlassian.com Shannon S
                        Votes:
                        29 Vote for this issue
                        Watchers:
                        54 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            jmoynihan Jamie (Inactive)
                            smackie@atlassian.com Shannon S
                            Affected customers:
                            29 This affects my team
                            Watchers:
                            54 Start watching this issue

                              Created:
                              Updated:
                              Resolved: