![]() ![]() WARNING: The configuration files were replaced by default configuration. WARNING: arguments transformed to: postgresql-setup -upgrade -unit postgresql WARNING: using obsoleted argument syntax, try -help ![]() Since by default it wanted to do en_US-UTF-8 on my system, but I needed en_GB-UTF-8, I needed to pass the parameters like this: ~]# PGSETUP_INITDB_OPTIONS="-locale=en_GB.UTF-8" postgresql-setup upgrade On RL8 system do: dnf install postgresql-server postgresql-upgradeĬopy the /var/lib/pgsql/data directory from your CentOS7 or RHEL7 system to /var/lib/pgsql/data directory on RL8 system. When I backup my databases using pg_dumpall ( pg_dumpall -c -U postgres > pg_dbs.bkp), is there a way to strip the encoding or change the encoding to I upgraded mine from postgres 9.2 to 10 like this: ![]() Is there an alternate way to set -locale=C using the postgresql-setup -initdb -unit postgresql command? With out using -locale=C, when I import my databases I get the encoding errors.ĮRROR: encoding “LATIN1” does not match locale “en_US.UTF-8”ĭETAIL: The chosen LC_CTYPE setting requires encoding “UTF8”. To initialize the postgres10 database, Rocky8 tutorials recommended using, postgresql-setup -initdb -unit postgresql which does not allow/recognise -locale=C. In the past, as the postgres user, I initialized the database with initdb -locale=C -D /var/lib/pgsql/data using locale=C to overcome UTF8 errors when restoring the database backup. I need to migrate my databases from the centOS7 with postgres9 to Rocky8.4 with postgres10. I realize this is more so Postgresql and not a Rocky linux problem, but perhaps someone knows. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |