Postgresql 中文操作指南

initdb

initdb - 创建新的 PostgreSQL 数据库集群

initdb — create a new PostgreSQL database cluster

Synopsis

initdb [ option …​] [ —​pgdata | -D ] directory

initdb [option…​] [ —​pgdata | -D ] directory

Description

initdb 创建新的 PostgreSQL [role="bare"]glossary.html#GLOSSARY-DB-CLUSTER database cluster 。

initdb creates a new PostgreSQL [role="bare"]glossary.html#GLOSSARY-DB-CLUSTERdatabase cluster.

创建数据库集群包括创建将存储集群数据的 [role="bare"]glossary.html#GLOSSARY-DATA-DIRECTORY directories ，生成共享目录表（属于整个集群而非特定数据库的表），以及创建 postgres 、 template1 和 template0 数据库。 postgres 数据库是默认数据库，供用户、实用程序和第三方应用使用。 template1 和 template0 作为源数据库，以后由 CREATE DATABASE 命令进行复制。永远不要修改 template0 ，但可以添加对象到 template1 ，默认情况下，这些对象将被复制到以后创建的数据库。有关详细信息，请参见 Section 23.3 。

Creating a database cluster consists of creating the [role="bare"]glossary.html#GLOSSARY-DATA-DIRECTORYdirectories 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. The postgres database is a default database meant for use by users, utilities and third party applications. template1 and template0 are meant as source databases to be copied by later CREATE DATABASE commands. template0 should never be modified, but you can add objects to template1, which by default will be copied into databases created later. See Section 23.3 for more details.

尽管 initdb 将尝试创建指定的数据目录，但如果所需数据目录的父目录为 root 所有，它可能没有权限。要在这种情况下初始化，请以 root 权限创建一个空数据目录，然后使用 chown 为数据库用户帐户分配该目录的所有权，然后 su 成为运行 initdb 的数据库用户。

Although 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. 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.

必须以将拥有服务器进程的用户的身份来运行 initdb ，因为服务器需要访问 initdb 创建的文件和目录。由于无法以 root 权限来运行服务器，因此也不得以 root 权限来运行 initdb 。（事实上它将拒绝这样做。）

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. Since the server cannot be run as root, you must not run initdb as root either. (It will in fact refuse to do so.)

由于安全原因， initdb 创建的新集群默认情况下仅由集群所有者可以访问。 —​allow-group-access 选项允许与集群所有者在相同组中的任何用户读集群中的文件。这对非特权用户执行备份非常有用。

For security reasons the new cluster created by initdb will only be accessible by the cluster owner by default. The —​allow-group-access option allows any user in the same group as the cluster owner to read files in the cluster. This is useful for performing backups as a non-privileged user.

initdb 初始化数据库集群的默认语言环境和字符集编码。当创建每个数据库时也可以单独为其设置这些内容。 initdb 为模板数据库确定这些设置，这些设置将作为所有其他数据库的默认设置。

initdb initializes the database cluster’s default locale and character set encoding. These can also be set separately for each database when it is created. initdb determines those settings for the template databases, which will serve as the default for all other databases.

默认情况下， initdb 使用语言环境提供程序 libc （参见 Section 24.1.4 ）。 libc 语言环境提供程序从环境中获取语言环境设置，并从语言环境设置中确定编码。

By default, initdb uses the locale provider libc (see Section 24.1.4). The libc locale provider takes the locale settings from the environment, and determines the encoding from the locale settings.

要为集群选择另一种语言环境，请使用选项 —​locale 。此外还有单独的选项 —​lc-* 和 —​icu-locale （参见下文）来设置各个语言环境类别的值。请注意，不同语言环境类别的设置不一致会导致无意义的结果，因此应谨慎使用。

To choose a different locale for the cluster, use the option —​locale. There are also individual options —​lc-* and —​icu-locale (see below) to set values for the individual locale categories. Note that inconsistent settings for different locale categories can give nonsensical results, so this should be used with care.

另外， initdb 可以使用 ICU 库通过指定 —​locale-provider=icu 来提供语言环境服务。必须使用 ICU 支持来构建服务器。要选择要应用的特定 ICU 语言环境 ID，请使用选项 —​icu-locale 。请注意，由于实现原因以及为了支持旧代码， initdb 在使用 ICU 语言环境提供程序时仍然会选择和初始化 libc 语言环境设置。

Alternatively, initdb can use the ICU library to provide locale services by specifying —​locale-provider=icu. The server must be built with ICU support. To choose the specific ICU locale ID to apply, use the option —​icu-locale. Note that for implementation reasons and to support legacy code, initdb will still select and initialize libc locale settings when the ICU locale provider is used.

当 initdb 运行时，它将打印出已选择设置的语言环境。如果您有复杂的要求或指定了多个选项，建议检查结果是否与预期相符。

When initdb runs, it will print out the locale settings it has chosen. If you have complex requirements or specified multiple options, it is advisable to check that the result matches what was intended.

可在 Section 24.1 中找到有关区域设置的更多详情。

More details about locale settings can be found in Section 24.1.

如需更改默认编码，请使用 —​encoding 。可在 Section 24.3 中找到更多详情。

To alter the default encoding, use the —​encoding. More details can be found in Section 24.3.

Options

  • -A _authmethod—​auth=_authmethod #

    • This option specifies the default authentication method for local users used in pg_hba.conf (host and local lines). See Section 21.1 for an overview of valid values.

    • initdb will prepopulate pg_hba.conf entries using the specified authentication method for non-replication as well as replication connections.

    • Do not use trust unless you trust all local users on your system. trust is the default for ease of installation.

  • —​auth-host=_authmethod_ #

    • This option specifies the authentication method for local users via TCP/IP connections used in pg_hba.conf (host lines).

  • —​auth-local=_authmethod_ #

    • This option specifies the authentication method for local users via Unix-domain socket connections used in pg_hba.conf (local lines).

  • -D _directory—​pgdata=_directory #

    • This option specifies the directory where the database cluster should be stored. This is the only information required by initdb, but you can avoid writing it by setting the PGDATA environment variable, which can be convenient since the database server (postgres) can find the data directory later by the same variable.

  • -E _encoding—​encoding=_encoding #

    • Selects the encoding of the template databases. This will also be the default encoding of any database you create later, unless you override it then. The character sets supported by the PostgreSQL server are described in Section 24.3.1.

    • By default, the template database encoding is derived from the locale. If —​no-locale is specified (or equivalently, if the locale is C or POSIX), then the default is UTF8 for the ICU provider and SQL_ASCII for the libc provider.

  • -g_—​allow-group-access_ #

    • Allows users in the same group as the cluster owner to read all cluster files created by initdb. This option is ignored on Windows as it does not support POSIX-style group permissions.

  • —​icu-locale=_locale_ #

    • Specifies the ICU locale when the ICU provider is used. Locale support is described in Section 24.1.

  • —​icu-rules=_rules_ #

    • Specifies additional collation rules to customize the behavior of the default collation. This is supported for ICU only.

  • -k_—​data-checksums_ #

    • Use checksums on data pages to help detect corruption by the I/O system that would otherwise be silent. Enabling checksums may incur a noticeable performance penalty. If set, checksums are calculated for all objects, in all databases. All checksum failures will be reported in the pg_stat_database view. See Section 30.2 for details.

  • —​locale=_locale_ #

    • Sets the default locale for the database cluster. If this option is not specified, the locale is inherited from the environment that initdb runs in. Locale support is described in Section 24.1.

  • —​lc-collate=_locale—​lc-ctype=_locale—​lc-messages=locale—​lc-monetary=locale—​lc-numeric=locale—​lc-time=locale #

    • Like —​locale, but only sets the locale in the specified category.

  • —​no-locale #

    • Equivalent to —​locale=C.

  • —​locale-provider={_libc|icu}_ #

    • This option sets the locale provider for databases created in the new cluster. It can be overridden in the CREATE DATABASE command when new databases are subsequently created. The default is libc (see Section 24.1.4).

  • -N_—​no-sync_ #

    • By default, initdb will wait for all files to be written safely to disk. This option causes initdb to return without waiting, which is faster, but means that a subsequent operating system crash can leave the data directory corrupt. Generally, this option is useful for testing, but should not be used when creating a production installation.

  • —​no-instructions #

    • By default, initdb will write instructions for how to start the cluster at the end of its output. This option causes those instructions to be left out. This is primarily intended for use by tools that wrap initdb in platform-specific behavior, where those instructions are likely to be incorrect.

  • —​pwfile=_filename_ #

    • Makes initdb read the bootstrap superuser’s password from a file. The first line of the file is taken as the password.

  • -S_—​sync-only_ #

    • Safely write all database files to disk and exit. This does not perform any of the normal initdb operations. Generally, this option is useful for ensuring reliable recovery after changing fsync from off to on.

  • -T _config—​text-search-config=_config #

  • -U _username—​username=_username #

    • Sets the user name of the [role="bare"]glossary.html#GLOSSARY-BOOTSTRAP-SUPERUSERbootstrap superuser. This defaults to the name of the operating-system user running initdb.

  • -W_—​pwprompt_ #

    • Makes initdb prompt for a password to give the bootstrap superuser. If you don’t plan on using password authentication, this is not important. Otherwise you won’t be able to use password authentication until you have a password set up.

  • -X _directory—​waldir=_directory #

    • This option specifies the directory where the write-ahead log should be stored.

  • —​wal-segsize=_size_ #

    • Set the WAL segment size, in megabytes. This is the size of each individual file in the WAL log. The default size is 16 megabytes. The value must be a power of 2 between 1 and 1024 (megabytes). This option can only be set during initialization, and cannot be changed later.

    • It may be useful to adjust this size to control the granularity of WAL log shipping or archiving. Also, in databases with a high volume of WAL, the sheer number of WAL files per directory can become a performance and management problem. Increasing the WAL file size will reduce the number of WAL files.

还提供其他一些不太常用的选项：

Other, less commonly used, options are also available:

  • -c _name=value—​set _name=value #

    • Forcibly set the server parameter name to value during initdb, and also install that setting in the generated postgresql.conf file, so that it will apply during future server runs. This option can be given more than once to set several parameters. It is primarily useful when the environment is such that the server will not start at all using the default parameters.

  • -d_—​debug_ #

    • Print debugging output from the bootstrap backend and a few other messages of lesser interest for the general public. The bootstrap backend is the program initdb uses to create the catalog tables. This option generates a tremendous amount of extremely boring output.

  • —​discard-caches #

    • Run the bootstrap backend with the debug_discard_caches=1 option. This takes a very long time and is only of use for deep debugging.

  • -L _directory_ #

    • Specifies where initdb should find its input files to initialize the database cluster. This is normally not necessary. You will be told if you need to specify their location explicitly.

  • -n_—​no-clean_ #

    • By default, when initdb determines that an error prevented it from completely creating the database cluster, it removes any files it might have created before discovering that it cannot finish the job. This option inhibits tidying-up and is thus useful for debugging.

其他选项：

Other options:

  • -V_—​version_ #

    • Print the initdb version and exit.

  • -?_—​help_ #

    • Show help about initdb command line arguments, and exit.

Environment

  • PGDATA #

    • Specifies the directory where the database cluster is to be stored; can be overridden using the -D option.

  • PG_COLOR #

    • Specifies whether to use color in diagnostic messages. Possible values are always, auto and never.

  • TZ #

    • Specifies the default time zone of the created database cluster. The value should be a full time zone name (see Section 8.5.3).

此实用程序与大多数其他 PostgreSQL 实用程序一样，还使用 libpq 支持的环境变量（请参阅 Section 34.15 ）。

This utility, like most other PostgreSQL utilities, also uses the environment variables supported by libpq (see Section 34.15).

Notes

也可以通过 pg_ctl initdb 调用 initdb 。

initdb can also be invoked via pg_ctl initdb.

See Also

pg_ctl 、 postgres 、 Section 21.1

pg_ctl, postgres, Section 21.1