On Mon, May 3, 2021, at 6:16 PM, kjohn...@eclypse.org wrote: > The next step in my testing is to create an empty bacula database on the > test system and restore it from the pg_dump file created on the conversion > system. I have learned that the bacula postgres database needs to have > encoding SQL_ASCII.
For what it's worth, SQL_ASCII was decided upon many years ago. > Here's the difficulty. As user bacula on the test system: > > $ export LC_ALL=C > $ createdb -E SQL_ASCII -T template0 bacula > createdb: database creation failed: ERROR: encoding "SQL_ASCII" does not > match locale "en_US.UTF-8" > DETAIL: The chosen LC_CTYPE setting requires encoding "UTF8". > > Probably, fixing this is something that everyone else knows. Unfortunately, > my Google searches find too much or almost nothing. A specific search of > the mailing list archive found a discussion of why SQL_ASCII was so > important (circa 2009), The decision was made earlier I think. > but not an answer to this problem. At least, not > one that I recognized. (same failure without the export, by the way). The > documentation for Bacula 7.4 > (https://www.bacula.org/7.4.x-manuals/en/main/Installing_Configuring_Post.ht > ml) also states that SQL_ASCII is essential, but I did not recognize a > solution to this problem there. I think the problem is more PostgreSQL & environment specific. Here is my test on FreeBSD 12.2 with PostgreSQL 12.6 - these commands are run as the postgres user: $ createdb -E SQL_ASCII -T template0 bacula $ dropdb bacula $ export LC_ALL=C $ createdb -E SQL_ASCII -T template0 bacula $ Works there. I suspect it is something specific to the environment. What do you have for this value? $ echo $locale $ -- Dan Langille d...@langille.org _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
