Installing Advanced Server with the Interactive Installer v11

You can use the Advanced Server interactive installer to install Advanced Server on Windows. The interactive installer is available from the EnterpriseDB website at:

https://www.enterprisedb.com/advanced-downloads

You can invoke the graphical installer in different installation modes to perform an Advanced Server installation:

• For information about using the graphical installer, see Performing a Graphical Installation on Windows.
• For information about performing an unattended installation, see Performing an Unattended Installation.
• For information about performing an installation with limited privileges, see Performing an Installation with Limited Privileges.
• For information about the command line options you can include when invoking the installer, see Reference - Command Line Options.

During the installation, the graphical installer copies a number of temporary files to the location specified by the TEMP environment variable. You can optionally specify an alternate location for the temporary files by modifying the TEMP environment variable.

If invoking the installer from the command line, you can set the value of the variable on the command line. Use the command:

SET TEMP=temp_file_location

Where temp_file_location specifies the alternate location for the temporary files and must match the permissions with the TEMP environment variable.

Setting Cluster Preferences during a Graphical Installation

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:

SET INITDBOPTS= -k -E=UTF-8

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 will supersede the value if specified in INITDBOPTS.

For more information about using initdb cluster configuration options, see the PostgreSQL Core Documentation available at:

https://www.postgresql.org/docs/11/static/app-initdb.html

In addition to the cluster configuration options documented in the PostgreSQL core documentation, Advanced Server supports the following initdb options:

--no-redwood-compat

--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 the Advanced Server in redwood compatibility mode to have access to all its Oracle compatibility features.

--redwood-like

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

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