This option specifies the default authentication method for local users used in lt_hba.conf (host and local lines). lt_initdb will prepopulate lt_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.

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

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

This option specifies the port for the database cluster. The default port is 5432.

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

Selects the encoding of the template database. This will also be the default encoding of any database you create later, unless you override it there. The default is derived from the locale, or SQL_ASCII if that does not work. The character sets supported by the LightDB server are described in Section 21.3.1.

Allows users in the same group as the cluster owner to read all cluster files created by lt_initdb.

Create a database cluster without extensions, which is equivalent to using lt_initdb directly.

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.

Used for Transparent Data Encryption. Before creating your database instance, you have to write some code to make sure that the key can be read by the database during startup and instance creation. The key is a 32-byte hex string.

Here is the most simplistic example possible:

    cat /somewhere/provide_key.sh
    #!/bin/sh
    echo 882fb7c12e80280fd664c69d2d636913
       

All you need is a program that prints the key to stdout. Make sure that LightDB is able to execute this program:

    chmod +x /somewhere/provide_key.sh
       

Note: You don't have to write a shell script – you can use any kind of executable such as a C, Go or Python.

Create the database instance:

    lt_initdb -p 5432 -D ./data -K /somewhere/provide_key.sh
       

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

Like --locale, but only sets the locale in the specified category.

Equivalent to --locale=C.

By default, lt_initdb will wait for all files to be written safely to disk. This option causes lt_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.

Makes lt_initdb read the database superuser's password from a file. The first line of the file is taken as the password.

Safely write all database files to disk and exit. This does not perform any of the normal lt_initdb operations.

Sets the default text search configuration. See default_text_search_config for further information.

Selects the user name of the database superuser. This defaults to the name of the effective user running lt_initdb. It is really not important what the superuser's name is, but one might choose to keep the customary name lightdb, even if the operating system user's name is different.

Makes lt_initdb prompt for a password to give the database 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.

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

Set the WAL segment size, in megabytes. This is the size of each individual file in the WAL log. The default size is 512 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.

Database cluster installation mode, there are three installation modes.

The default installation mode is single.

Database cluster compatibility type, there are three compatibility types:

The default compatibility type is off.

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 lt_initdb uses to create the catalog tables. This option generates a tremendous amount of extremely boring output.

Specifies where lt_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.

By default, when lt_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.

Print the lt_initdb version and exit.

Show help about lt_initdb command line arguments, and exit.

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

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

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