8.3 KiB
PostgreSQL Cheat-Sheet
PostgreSQL or also known as Postgres, is a free and open-source relational database management system. PostgreSQL features transactions with Atomicity, Consistency, Isolation, Durability (ACID) properties automatically updatable views, materialized views, triggers, foreign keys, and stored procedures. It is designed to handle a range of workloads, from single machines to data warehouses or web services with many concurrent users.
Installation
Install PostgreSQL on Debian/Ubuntu/Mint/Zorin/forks
sudo apt update
sudo apt install -y postgresql postgresql-contrib postgresql-client
sudo systemctl status postgresql.service
Install PostgreSQL on RHEL/Fedora/CentOS/Alma/Rocky
sudo dnf update
sudo dnf install -y postgresql-server
Install PostgreSQL on Arch/Manjaro/Arco/forks
sudo pacman -Syyu
sudo pacman -S postgresql --noconfirm
Deploy PostgreSQL in Docker
Deploy PostgreSQL on Kubernetes with Zalando Postgres Operator
Postgres is probably the database which is most common on Cloud platforms and also, running on Kubernetes environments. There are several so called "Kubernetes Operators" which handle the deployment of Postgres clusters for you. One of it is the Postgres Operator by Zalando.
You can find some tutorials regarding deployment of the operator and how to work with it, in the link list below:
- Deploy Zalando Postgres Operator on your Kubernetes cluster
- Configure Zalando Postgres Operator Backup with WAL-G
- Configure Zalando Postgres Operator Restore with WAL-G
Connecting to Postgres
Connect to local Postgres instance
A local connection (from the database server) can be done by the following command:
sudo -u postgres psql
Connect to remote Postgres instance
Note, that you first have to install the postgresql-client package, (postgresql via Homebrew on macOS) on the client machine. A connection from a remote host can be done by the following command:
psql -h {pg_host} -U {username} -d {database} -p {port}
Set password for postgres database user
The password for the postgres database user can be set the the quickcommand \password or by alter user postgres password 'Supersecret'. A connection using the postgres user is still not possible from the "outside" hence to the default settings in the pg_hba.conf.
Update pg_hba.conf to allow postgres user connections with password
In order to allow connections of the postgres database user not using OS user authentication, you have to update the pg_hba.conf which can be found under /etc/postgresql/12/main/pg_hba.conf.
sudo vi /etc/postgresql/12/main/pg_hba.conf
...
local all postgres peer
...
Change the last section of the above line to md5.
local all postgres md5
A restart is required in order to apply the new configuration:
sudo systemctl restart postgresql
Now a connection from outside the database host is possible e.g.
psql -U postgres -d postgres -h databasehostname
Creation of additional database users
A database user can be created by the following command:
create user myuser with encrypted password 'Supersecret';
CREATE ROLE
postgres=# \du
List of roles
Role name | Attributes | Member of
-----------+------------------------------------------------------------+-----------
myuser | | {}
postgres | Superuser, Create role, Create DB, Replication, Bypass RLS | {}
Creation of additional databases
One can create new Postgres databases within an instance. Therefore you can use the psql command to login (see above).
CREATE DATABASE dbname OWNER myuser;
CREATE DATABASE
postgres=# \l
List of databases
Name | Owner | Encoding | Collate | Ctype | Access privileges
-----------+----------+----------+-------------+-------------+-----------------------
dbname | myuser | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
template0 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres +
| | | | | postgres=CTc/postgres
template1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres +
| | | | | postgres=CTc/postgres
You can leave the OWNER section of the command, when doing so, the current user will become owner of the newly created database.
To change the owner of an existing database later, you can use the following command:
postgres=# alter database dbname owner to myuser;
ALTER DATABASE
Backup and Restore
There are near to endless combinations in tools and parameters to backup postgres databases. Below you can find some examples using the Postgres built-in tools pgdump, pg_basebackup and pg_restore.
pg_dump / pg_dumpall
Using pg_dump or pg_dumpall enables you to extract / export a PostgreSQL database(s) into a (SQL) script file or a custom archive file.
pg_dump
The following command creates a custom archive file from a database specified with -d. To export data in custom format, you have to specify so with the -F c option. Custom file dumps have the benefit, that they are compressed by default.
Using the `--create` option will include the SQL commands in the dump script that will create the database before importing it later. The `-Z 9` option in this example compresses the SQL script created with the highest available compression rate (`0-9`).
```bash
pg_dump -h vmdocker -U awx -d awx --create -f -Z 9 /tmp/awx_dump.sql.gz
The following command creates a custom archive file from a database specified with -d. To export data in custom format, you have to specify so with the -F c option. Custom file dumps have the benefit, that they are compressed by default.
pg_dump -h {pg_host} -U {username} -d {database} -F c -f /pg_dump/dumpfile.dmp
Custom format files can only be restored by pg_restore (see below). A SQL dump can be restored by using psql.
psql -d newdb -f db.sql
A complete guide of pg_dump from the official documentation can be found here.
pg_dumpall
A full dump of all databases of a Postgres instance can be done by pg_dumpall. It will include also user creation information.
A difference to pg_dump, you cannot choose for different output formats. pg_dumpall will always create a SQL script as output. Therefore,
you don't need pg_restore for restoring a "full" dump. Only psql is needed (see below).
pg_dumpall -h {pg_host} -U postgres > database.out
If you use password authentication it will ask for a password each time. It is convenient to have a ~/.pgpass file or PGPASSWORD environment variable set.
So importing a full dump is really easy by the following psql command:
psql -h {pg_host} -f databaseb.out -U postgres
A complete guide of pg_dumpall from the official documentation can be found here.
pg_restore
pg_restore can be used to restore custom file dumps created by pg_dump.
The following command will create the database (which has been dumped before).
pg_restore -h {pg_host} -U {pg_user} -d postgres --create -F c /tmp/db.dmp -v
A complete guide of pg_restore from the official documentation can be found here.