Backing up PostgreSQL data by continuous archiving"Ĥ.6.3.1. Backing up PostgreSQL data by continuous archiving"Ĭollapse section "4.6.3. Backing up PostgreSQL data by continuous archivingĮxpand section "4.6.3. Performing file system level backing upĤ.6.3. Advantages and limitations of file system backing upĤ.6.2.2. Backing up PostgreSQL data with a file system level backup"Ĥ.6.2.1. Backing up PostgreSQL data with a file system level backup"Ĭollapse section "4.6.2. Backing up PostgreSQL data with a file system level backupĮxpand section "4.6.2. Performing an SQL dump of a database on another serverĤ.6.1.7. Restoring databases dumped using pg_dumpallĤ.6.1.6. Restoring a database dumped using pg_dumpĤ.6.1.5. Performing an SQL dump using pg_dumpallĤ.6.1.4. Performing an SQL dump using pg_dumpĤ.6.1.3. Advantages and disadvantages of an SQL dumpĤ.6.1.2. Backing up PostgreSQL data with an SQL dump"Ĥ.6.1.1. Backing up PostgreSQL data with an SQL dump"Ĭollapse section "4.6.1. Backing up PostgreSQL data with an SQL dumpĮxpand section "4.6.1. Backing up PostgreSQL data"Ĭollapse section "4.6. Configuring TLS encryption on a PostgreSQL serverĮxpand section "4.6. Connecting the replica server to the source serverĤ.5. Creating a replication user on the MySQL source serverģ.6.4. Migrating to a RHEL 9 version of MySQL 8.0Ĭollapse section "3.6. Performing logical backup with mysqldumpģ.5. Backing up MySQL data"Ĭollapse section "3.4. Adding a new node to MariaDB Galera ClusterĮxpand section "3.4. Components to build MariaDB Galera ClusterĢ.8.4. Introduction to MariaDB Galera ClusterĢ.8.2. Replicating MariaDB with Galera"Ĭollapse section "2.8. Migrating from a RHEL 8 version of MariaDB 10.3 to a RHEL 9 version of MariaDB 10.5Įxpand section "2.8. Notable differences between MariaDB 10.3 and MariaDB 10.5Ģ.7.2. Migrating to MariaDB 10.5"Ĭollapse section "2.7. Restoring data using the Mariabackup utilityĮxpand section "2.7. Performing physical online backup using the Mariabackup utilityĢ.6.3. Performing logical backup with mariadb-dumpĢ.6.2. Backing up MariaDB data"Ĭollapse section "2.6. Configuring the MariaDB client to use TLS encryption by defaultĮxpand section "2.6. Globally enabling TLS encryption in MariaDB clients"Ģ.5.1. Globally enabling TLS encryption in MariaDB clients"Ĭollapse section "2.5. Globally enabling TLS encryption in MariaDB clientsĮxpand section "2.5. Requiring TLS encrypted connections for specific user accountsĢ.5. Configuring TLS on a MariaDB serverĢ.4.3. Placing the CA certificate, server certificate, and private key on the MariaDB serverĢ.4.2. Setting up TLS encryption on a MariaDB server"Ģ.4.1. Setting up TLS encryption on a MariaDB server"Ĭollapse section "2.4. Setting up TLS encryption on a MariaDB serverĮxpand section "2.4. That solved my problem ( see also this problem).Providing feedback on Red Hat documentationĢ.4. The newt thing is to tell PostGreSQL that template0 is a template and that you don't have to be the owner of the database to copy it: UPDATE pg_database SET datistemplate = TRUE WHERE datname = 'template0' So, I resolved to clone template0 with new locale settings and replace the existing template0 with its clone: CREATE DATABASE template0b TEMPLATE template0 LC_COLLATE 'C' LC_CTYPE 'C' ĪLTER DATABASE template0b RENAME TO template0 The problem is that locale settings can't be changed at all. So I tried: ALTER DATABASE template0 SET LC_CTYPE TO 'C' ĪLTER DATABASE template0 SET LC_COLLATE TO 'C' The simple solution would be to change the locale settings from template0. This was probably because LC_ALL was not set to C when the databases were initialized with initdb. And the encoding is incompatible with these locale settings. In that particular case, the locale information from the template is used for the new database. With the flag -e we can se it is issuing the following command to the server: CREATE DATABASE gnattracker ENCODING 'SQL_ASCII' TEMPLATE template0 The problem is that createdb vdoesn't read the environment variable LC_ALL when a template database is used. Thanks voretaq7, now I understand the problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |