< Previous | Contents | Next >
5.3.3. Configuring PostgreSQL Databases
PostgreSQL is a database server. It is rarely useful on its own but is used by many other services to store data. Those services will generally access the database server over the network and usually require authentication credentials to be able to connect. Setting up those services thus requires creating PostgreSQL databases and user accounts with appropriate privileges on the database. To be able to do that, we need the service to be running, so let’s start it with systemctl start postgresql.
Multiple PostgreSQL The PostgreSQL packaging allows for multiple versions of the database server to be versions supported co-installed. It is also possible to handle multiple clusters (a cluster is a collection of databases served by the same postmaster). To achieve this, the configuration files
are stored in /etc/postgresql/version/cluster-name/.
In order for clusters to run side-by-side, each new cluster gets assigned the next avail- able port number (usually 5433 for the second cluster). The postgresql.service file is an empty shell, making it easy to act on all clusters together as each cluster has its own unit (postgresql@version-cluster.service).
Multiple PostgreSQL The PostgreSQL packaging allows for multiple versions of the database server to be versions supported co-installed. It is also possible to handle multiple clusters (a cluster is a collection of databases served by the same postmaster). To achieve this, the configuration files
are stored in /etc/postgresql/version/cluster-name/.
In order for clusters to run side-by-side, each new cluster gets assigned the next avail- able port number (usually 5433 for the second cluster). The postgresql.service file is an empty shell, making it easy to act on all clusters together as each cluster has its own unit (postgresql@version-cluster.service).