Installing PostgreSQL for i2 Analyze

Location

If you are creating a production deployment, you can install PostgreSQL in any location. When you install PostgreSQL, record the location of the installation directory because you must specify this location in the deployment toolkit before you can deploy i2 Analyze.

If you are creating an example deployment, install PostgreSQL (server and client) in the following location:

• For Windows: C:/Program Files/PostgreSQL/16

• For Linux: /usr/lib/postgresql/16

In addition, an example deployment needs the PostgreSQL database server to listen on (the default) port 5432.

Collation

In PostgreSQL, the collation settings that determine the case- and accent-sensitivity of comparisons in a database (for example, whether Cafe matches café) are set at creation and cannot be changed without re-creating the database.

Important: Before any deployment of i2 Analyze with the Chart Store or the Information Store, read the documentation about the Collation_Deterministic, Collation_Locale, and Collation_Sensitivity settings in InfoStoreNamesPostgres.properties and change the default values if you need to.

Other features

All installations of PostgreSQL for use with i2 Analyze must include the PostGIS (geospatial) extension.

Note: PostgreSQL packages and installers are available with and without PostGIS. For these and other downloads associated with PostgreSQL, see the official download page at https://www.postgresql.org/download.

If you already have a PostgreSQL installation that does not include PostGIS, you can add the extension to the existing installation. For more information, see the PostGIS documentation at https://postgis.net/install/.

Note: When you add PostGIS to an existing installation that includes pgAudit, you must temporarily disable pgAudit first. Otherwise, PostGIS fails to install.

The PostgreSQL client Command Line Tools (that is, psql) must be installed on the same server as the i2 Analyze toolkit. On Windows, this installation is called the "Command Line Tools". On Linux, it's just referred to as the "client".

PostgreSQL does not have a built-in scheduling agent. If you need to be able to run tasks such as deletion by rule on an automated schedule, you must install a third-party tool such as pg_cron.

Users

The PostgreSQL database user that you specify in credentials.properties must be a superuser, and it must have all available privileges enabled.

The PostgreSQL installation process creates a suitable user that has the name postgres and a password that you specify during the procedure.

High availability

At this version of i2 Analyze, PostgreSQL is not supported in deployments for which HADR is required.