initdb determines those settings for the template databases, which will serve as the default for all other databases.īy default, initdb uses the locale provider libc (see Section 24.1.4). These can also be set separately for each database when it is created. Initdb initializes the database cluster's default locale and character set encoding. This is useful for performing backups as a non-privileged user. The -allow-group-access option allows any user in the same group as the cluster owner to read files in the cluster. (It will in fact refuse to do so.)įor security reasons the new cluster created by initdb will only be accessible by the cluster owner by default. Since the server cannot be run as root, you must not run initdb as root either. Initdb must be run as the user that will own the server process, because the server needs to have access to the files and directories that initdb creates. To initialize in such a setup, create an empty data directory as root, then use chown to assign ownership of that directory to the database user account, then su to become the database user to run initdb. See Section 23.3 for more details.Īlthough initdb will attempt to create the specified data directory, it might not have permission if the parent directory of the desired data directory is root-owned. template0 should never be modified, but you can add objects to template1, which by default will be copied into databases created later. template1 and template0 are meant as source databases to be copied by later CREATE DATABASE commands. The postgres database is a default database meant for use by users, utilities and third party applications. import_db_l9_schemadb_l9.Initdb creates a new PostgreSQL database cluster.Ĭreating a database cluster consists of creating the directories in which the cluster data will live, generating the shared catalog tables (tables that belong to the whole cluster rather than to any particular database), and creating the postgres, template1, and template0 databases. Obviously it's necessary to grant the same privilege.ģ) Restore data to the new database: nohup psql -d DBNAME_L9 -p XXXX -a -f ./dump_db_schemadb_l9.sql -o. LC_COLLATE = LC_CTYPE = TEMPLATE = template0 TABLESPACE =. So we need to update something in the schema, like data or comments.Ģ) Now create a new database DBNAME_L9 with the different encoding: CREATE DATABASE DBNAME_L9 WITH ENCODING 'LATIN9' owner. If you have more than a schema, make dump of database!!ġ) We can make it in one step: nohup pg_dump -d DBNAME -p XXXX -b -v -n schemadb -E LATIN9 -file=./dump_db_schemadb_l9.sql &īut sometimes it might fail, with ERROR: character with byte sequence 0xef 0xbf 0xbd in encoding "UTF8" has no equivalent in encoding "LATIN9". LC_COLLATE = we have just one schema in DBNAME: schemadb, as I had.ġ) First of all we need to create a backup of it. With server encoding: SHOW SERVER_ENCODING Īnd we have a database DBNAME: postgres=# SELECT datname, pg_encoding_to_char(encoding) AS encoding, datcollate, datctype FROM pg_database WHERE datname ='DBNAME' ĭBNAME | UTF8 | en_US.UTF-8 | en_US.UTF-8īut we need to change it in: ENCODING = 'LATIN9' Template0 | UTF8 | en_US.UTF-8 | en_US.UTF-8 Assuming the default encoding of the template databases is set to UTF8: postgres=# SELECT datname, pg_encoding_to_char(encoding) AS encoding, datcollate, datctype FROM pg_database WHERE datname ='template0' ĭatname | encoding | datcollate | datctype
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |