Setting cluster preferences during a graphical installation v16

During an installation, the graphical installer invokes the PostgreSQL initdb utility to initialize a cluster. If you are using the graphical installer, you can use the INITDBOPTS environment variable to specify your initdb preferences. Before invoking the graphical installer, set the value of INITDBOPTS at the command line, specifying one or more cluster options. For example:


If you specify values in INITDBOPTS that are also provided by the installer (such as the –D option, which specifies the installation directory), the value specified in the graphical installer supersedes the value if specified in INITDBOPTS.

For more information about using initdb cluster configuration options, see the PostgreSQL core documentation. In addition to the cluster configuration options documented in the PostgreSQL core documentation, EDB Postgres Advanced Server supports the following initdb options:


--no-redwood-compat instructs the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser is postgres and the name of the default database is postgres. A small subset of Advanced Server features compatible with Oracle databases are available with this mode. However, we recommend using Advanced Server in redwood compatibility mode to have access to all its Oracle compatibility features.


--redwood-like instructs the server to use an escape character (an empty string ('')) following the LIKE (or PostgreSQL compatible ILIKE) operator in a SQL statement that is compatible with Oracle syntax.


--icu-short-form creates a cluster that uses a default ICU (International Components for Unicode) collation for all databases in the cluster. For more information about Unicode collations, see Basic Unicode collation algorithm concepts.