Enterprisedb installation guide

If you have built the Postgres installation from source, you are required to manually create a service script. While the PEM server installer checks for the presence of the service script, it does not check the integrity of the script itself; for PEM to function properly, you must ensure that the service script works as expected.

The service script must be able to start, stop and restart the database server. Service scripts are platform-specific; you can find a sample service script for Linux in Linux Service Script Sample section.

For information about customizing a Postgres service, visit:. If you are using Windows to host the PEM backend database, you must register the name of the Postgres server with the Windows service manager. If you are using a Postgres server that was created using an EnterpriseDB installer, the service will be registered automatically. The syntax of the command is:. Postgres core documentation. After preparing the existing Postgres server, invoke the PEM server installer.

Assume superuser or, on Windows, Administrative privileges and navigate into the directory that contains the installer. Then, invoke the installer with the command:. Carefully review the license agreement before highlighting the appropriate radio button and accepting the agreement; click Next to continue to the Installation Directory dialog. Use the Installation Directory dialog to specify the location of the PEM server and access the Advanced options dialog:.

Use the Installation Directory field to open a browser dialog and select the directory in which the PEM server will be installed. If you are installing the PEM server on an existing server, check the box next to Show advanced options to instruct the installer to include the Advanced options dialog in the installation process.

Use the radio buttons on the Advanced options dialog to specify an installation type. See Installing Web Services section for more information about invoking this option. Database if you are installing only the PEM server and creating the pem backend database on the current host. Select the name of a Postgres server on the current host that was installed using a Postgres one-click installer or Advanced Server installer.

The selected database server must include an installation of the sslutils contrib module, and have a startup script on Linux or a registered service on Windows. For information about Preparing the Postgres Server, please see this section. Enter the port number on which the Postgres server listens in the Port field.

Enter the name of a database superuser in the User field. Enter the password associated with the superuser in the Password field. Enter the name of the service script for the Postgres server in the Service Name field. For information about preparing a service script, please see this section. The PEM server installer will install a PEM agent to the host on which the server resides, to monitor the server and provide alert processing and garbage collection services. The command line options of the PEM server and PEM agent installers offer functionality in situations where a graphical installation may not work because of limited resources or system configuration.

Include the --mode unattended option when invoking the installer to perform an installation without additional user input. Include the --mode text option when invoking the installer to perform an installation from the command line with an interactive installer. Not all command line options are suitable for all platforms.

For a complete reference guide to the command line options, include the --help option when you invoke the installer. You can perform an unattended PEM server installation by providing installation preferences on the command line when invoking the installer. Please note that the system on which you are installing the PEM server must have internet access. You must have Administrative privileges to install the PEM server. Before invoking the PEM server installer, you must install the following dependencies:.

You can use the PEM server installer to satisfy the dependencies of the PEM server; use the following command to extract the dependencies. Navigate to the location of the installer, and use the following command to extract the dependencies:. After extracting the files, you must install each program. To register, visit the EDB website. You may wish to specify a network range for example, You can invoke the PEM server installer at the command line to perform an interactive installation if your system does not support a full graphical installation.

Please note that the system on which you are installing PEM must have internet access. After extracting the files, you must install each program; navigate into the directory that contains the files, and enter:. The example that follows demonstrates performing a text-mode installation on a Linux system; the installation process on a Windows system is similar. After accepting the license agreement, you will be prompted for the name and address of a registered EnterpriseDB user; provide the information when prompted:.

Next, you will be prompted for an installation directory; you can use the default installation directory, or specify an alternate location. Use the Agent Details fields to specify a descriptive name for the agent and the location of the agent certificate:. The installer will prompt you before it proceeds with the installation; press Return to start the installation:. Installing Postgres Enterprise Manager. This is the simplest PEM server installation option. Note You may be required to add the sslutils package to your installation.

Note The current host may not be the host of the PEM backing database. Note The steps that follow should be considered guidelines only; the actual steps required to configure your Postgres installation will vary depending on the configuration of your Postgres server. On Linux If the Postgres server resides on a Linux system, you must use the gcc compiler to build sslutils. Use yum to install gcc: yum install gcc. Note The selected database server must include an installation of the sslutils contrib module, and have a startup script on Linux or a registered service on Windows.

Note For information about preparing a service script, please see this section. Check the box next to Register now? Specify the name of the database superuser in the User Name field.

Specify the password associated with the database superuser in the Password field. Click Next to continue to pemAgent Service Account. The installer will attempt to connect to the server to verify that the details are correct. Provide the password for the edb account under which the pemAgent service will run.

Click Next to continue to Agent Details dialog. The tree control displayed in the Browser panel of the PEM web interface displays the value entered in the Description field to identify the PEM agent. Provide a descriptive name, or accept the default provided by the PEM agent host, and click Next to continue. If you checked the Show advanced options checkbox, the Advanced options dialog opens.

Specify an alternate path for the certificate or accept the default and click Next. Since version 1. The latter don't require a restart of the PostgreSQL instance and, as a result, a switchover in the cluster.

This behavior, which is disabled by default, is described below. The new instance manager shipped with the operator is added to each PostgreSQL pod via an init container. However, this behavior can be changed via configuration to enable in-place updates of the instance manager, which is the PID 1 process that keeps the container alive.

Internally, any instance manager from version 1. When the new instance manager restarts using the new binary, it adopts the already running postmaster. As a result, the PostgreSQL process is unaffected by the update, refraining from the need to perform a switchover.

The other side of the coin, is that the Pod is changed after the start, breaking the pure concept of immutability. The in-place upgrade process will not change the init container image inside the Pods.

Therefore, the Pod definition will not reflect the current version of the operator. Every release of the operator within the same API version is compatible with the previous one. The current API version is v1, corresponding to versions 1.

In addition to new features, new versions of the operator contain bug fixes and stability enhancements. Because of this, we strongly encourage users to upgrade to the latest version of the operator , as each version is released in order to maintain the most secure and stable Postgres environment. If you are unable to apply updates as each version becomes available, we recommend upgrading through each version in sequential order to come current periodically and not skipping versions.

The release notes page contains a detailed list of the changes introduced in every released version of Cloud Native PostgreSQL, and it must be read before upgrading to a newer version of the software. Most versions are directly upgradable and in that case, applying the newer manifest for plain Kubernetes installations or using the native package manager of the chosen distribution is enough. When versions are not directly upgradable, the old version needs to be removed before installing the new one.