Installing EDB Postgres Advanced Server on SLES 15 x86_64 v17

Prerequisites

Before you begin the installation process:

• Set up the EDB repository.

  Setting up the repository is a one-time task. If you already set up your repository, you don't need to perform this step.

  To determine if your repository exists, enter:

  zypper lr -E | grep enterprisedb

  If no output is generated, the repository is installed.

  To set up the EDB repository:

  1. Go to EDB repositories.

  2. Select the button that provides access to the EDB repository.

  3. Select the platform and software that you want to download.

  4. Follow the instructions for setting up the EDB repository.

• Activate the required SUSE module:

  → WrapCopy

  sudo SUSEConnect -p PackageHub/15.7/x86_64

• Refresh the metadata:

  → WrapCopy

  sudo zypper refresh

Install the package

sudo zypper -n install edb-as<xx>-server

Where <xx> is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 17, the package name would be edb-as17-server.

Optionally, enable the development SUSE modules only if required:

sudo SUSEConnect -p sle-module-desktop-applications/15.7/x86_64
sudo SUSEConnect -p sle-module-development-tools/15.7/x86_64
sudo zypper install edb-as<xx>-server-devel

Where <xx> is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 17, the package name would be edb-as17-server.

To install an individual component:

sudo zypper -n install <package_name>

Where package_name can be any of the available packages from the available package list.

See excluding/including the packages to exclude or include an individual package while installing the EDB Postgres Advanced Server.

Initial configuration

Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password.

First, you need to initialize and start the database cluster. The edb-as-17-setup script creates a cluster in Oracle-compatible mode with the edb sample database in the cluster. To create a cluster in Postgres mode, see Initializing the cluster in Postgres mode.

sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as17/bin/edb-as-17-setup initdb

sudo systemctl start edb-as-17

To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.

sudo su - enterprisedb

psql edb

The server runs with the peer or ident permission by default. You can change the authentication method by modifying the pg_hba.conf file.

Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see Modifying the pg_hba.conf file.

ALTER ROLE enterprisedb IDENTIFIED BY password;

Experiment

Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table.

First, use psql to create a database named hr to hold human resource information.

# running in psql
CREATE DATABASE hr;

CREATE DATABASE

Connect to the hr database inside psql:

\c hr

psql (17.0.0, server 17.0.0)
You are now connected to database "hr" as user "enterprisedb".

Create columns to hold department numbers, unique department names, and locations:

CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk
PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc
varchar(13));

CREATE TABLE

Insert values into the dept table:

INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');

INSERT 0 1

INSERT into dept VALUES (20,'RESEARCH','DALLAS');

INSERT 0 1

View the table data by selecting the values from the table:

SELECT * FROM dept;

deptno  |   dname    |   loc
--------+------------+----------
10      | ACCOUNTING | NEW YORK
20      | RESEARCH   | DALLAS
(2 rows)