Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Confluence
  3. After Update to 2.7.1 of the app : The database collation 'C' is not supported by Confluence.

After Update to 2.7.1 of the app : The database collation 'C' is not supported by Confluence.

Scheduled Pinned Locked Moved Solved Confluence
postgresql
8 Posts 2 Posters 1.6k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? Offline
      ? Offline
      A Former User
      wrote on last edited by girish
      #1

      I got a admin message after login:

      Database: The database collation 'C' is not supported by Confluence. We recommend utf-8. On Windows you can also use the Windows-1252 collation for your locale.
      

      can this be ignored? Should i change this setting?

      Regards Jens

      1 Reply Last reply
      0
      • girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #2

        Indeed, the default collation in the postgres addon is 'C'

        db5b92d92c20f2448fa4a3388cd74ba0af=> select datname, datcollate from pg_database;
                      datname               | datcollate 
        ------------------------------------+------------
         postgres                           | C
         template1                          | C
         template0                          | C
         db5b92d92c20f2448fa4a3388cd74ba0af | C
        (4 rows)
        

        My understanding was that apps can set collation on a per table basis anyway and this is why it hasn't been a problem so far. I can switch the default collation to utf8, i guess. Or maybe we need this information in the manifest. I will check what is the best approach.

        1 Reply Last reply
        0
        • girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #3

          There's an even better command \l.

          db5b92d92c20f2448fa4a3388cd74ba0af=> \l
                                                                                             List of databases
                          Name                |                Owner                 | Encoding | Collate | Ctype |                               Access privileges                               
          ------------------------------------+--------------------------------------+----------+---------+-------+-------------------------------------------------------------------------------
           db5b92d92c20f2448fa4a3388cd74ba0af | user5b92d92c20f2448fa4a3388cd74ba0af | UTF8     | C       | C     | user5b92d92c20f2448fa4a3388cd74ba0af=CTc/user5b92d92c20f2448fa4a3388cd74ba0af
           postgres                           | postgres                             | UTF8     | C       | C     | 
           template0                          | postgres                             | UTF8     | C       | C     | =c/postgres                                                                  +
                                              |                                      |          |         |       | postgres=CTc/postgres
           template1                          | postgres                             | UTF8     | C       | C     | postgres=CTc/postgres
          (4 rows)
          
          1 Reply Last reply
          0
          • girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by
            #4

            I have changed the collation to C.UTF-8 explicitly for the next release. For the moment, you can ignore the warning.

            1 Reply Last reply
            1
            • ? Offline
              ? Offline
              A Former User
              wrote on last edited by
              #5

              OK,
              thanks for your Support.

              1 Reply Last reply
              0
              • girishG Offline
                girishG Offline
                girish
                Staff
                wrote on last edited by
                #6

                @jensbee4 In postgres, one cannot change the collation and ctype of an existing database. The change I have made changes the type for new installations. So, what you have to do after the next release is to make a backup of the confluence app and clone it to a new location (this will create a db with the correct collation) and move the clone back to the original location (after you confirm it's working).

                ? 1 Reply Last reply
                0
                • girishG girish

                  @jensbee4 In postgres, one cannot change the collation and ctype of an existing database. The change I have made changes the type for new installations. So, what you have to do after the next release is to make a backup of the confluence app and clone it to a new location (this will create a db with the correct collation) and move the clone back to the original location (after you confirm it's working).

                  ? Offline
                  ? Offline
                  A Former User
                  wrote on last edited by
                  #7

                  @girish
                  Hi, the next release is Confluence Package v2.8.0, App v7.8.0?
                  I will do the Backup and reinstall at Friday.

                  Regards Jens

                  1 Reply Last reply
                  0
                  • girishG Offline
                    girishG Offline
                    girish
                    Staff
                    wrote on last edited by
                    #8

                    @jensbee4 you have to wait for next cloudron release. The change is part of cloudron 5.6.2 (see the announcement category).

                    1 Reply Last reply
                    0
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Bookmarks
                      • Search