# Release notes

## Release notes

## DMK for PostgreSQL 2.5.0

### New features

* The CIS script is now written in Go (it was written in Python in previous releases)
* Added pgHero exmaple ( this can be found here: containers/pghero/ )

#### Updated templates

* Switch the Patroni and ETCD templates to use SSL by default
* Added a new template to create a self signe CA and the certificates ( ssl\_cert\_gen.txt )
* Updated the pgBackRest commands template to include examples for "restore" operations
* Updated the Prometheus and Grafane template to the latest version and fixed some commands
* Updated the PostGIS installation template for RHEL9
* Set jit=off in the postgresql.auto.conf template

#### New SQL scripts

* Added a script to describe a page/block: get\_page\_descipription.sql

## DMK for PostgreSQL 2.4.0

### New features

* Add a script to list the SWAP usage per process (swap\_usage.sh)
* Add a script to list tables which are close to wraparound (how\_tables\_close\_to\_wraparound.sql)
* Add a script which loads the PostgreSQL log file into a table (create\_and\_load\_log\_tables.sql)
* Add a script to set the SELinux context (set\_selinux\_context.sh)

#### Updated templates

* Adapt package list for SLES / openSUSE 16
* Adapt package list for RHEL 10
* Add an example for ldap authentication (ldap.txt)
* Add allowlist to Patroni template
* Add new Patroni 4.1.0 parameters to the template
* Add missing packages for Debian 13
* Remove wal\_keep\_segments from postgresql.auto.conf and patroni.yml
* Aligned patroni.yml and postgresql.auto.conf

## DMK for PostgreSQL 2.3.0

### New features

#### Updated templates

* The tuning profile comes with new and adjusted parameters
* The package list for SLES15 based systems has been updated
* The package list for the upcoming Debian 13 has been added
* The ectd template now comes with instructions how to handle proxied environments
* The ectd template comes with adjusted compaction parameters to handle larger etcd databases by default
* Update the PostGIS build instructions with the latest minor releases
* Enable new features for PostgreSQL 18: io\_uring, oauth and NUMA
* Move the autoconf way of building PostgreSQL into a separate template
* Extend the postgresql.auto.conf template: Enable io\_uring, set io\_combine\_limit, set min\_dynamic\_shared\_memory

## DMK for PostgreSQL 2.2.x

The 2.2.0 release was an internal maintenance release due to changes in the build pipelines.

## DMK for PostgreSQL 2.1.x

### # New features

#### # Give more control how to display the instance overview

Traditionaly the instance overview looks like this:

```
 PostgreSQL Clusters up and running on this host: 
 ---------------------------------------------------------------------------------------------- 
    pgdev       ->  /u02/pgdata/PGDEV                                        ->  5432  ==> OPEN     
 
 PostgreSQL Clusters NOT running on this host: 
 ---------------------------------------------------------------------------------------------- 
    pg94        ->  /u02/pgdata/94                                           ->  3998  ==> CLOSED       
    pg95        ->  /u02/pgdata/95                                           ->  3999  ==> CLOSED       
    pg96        ->  /u02/pgdata/96                                           ->  4000  ==> CLOSED       
    pg10        ->  /u02/pgdata/10                                           ->  4001  ==> CLOSED       
    pg11        ->  /u02/pgdata/11                                           ->  4002  ==> CLOSED       
    pg12        ->  /u02/pgdata/12                                           ->  4003  ==> CLOSED       
    pg13        ->  /u02/pgdata/13                                           ->  4004  ==> CLOSED       
    pg14        ->  /u02/pgdata/14                                           ->  4005  ==> CLOSED       
    pg15        ->  /u02/pgdata/15                                           ->  4006  ==> CLOSED       
    pg16        ->  /u02/pgdata/16                                           ->  4007  ==> CLOSED  
```

With the release of DMK for PostgreSQL 2.1.0 the user has more control about how to display this overview. There are two additional switches to "dmk-run-pl" which is behind the "u" and "ser" aliases:

```
postgres@pgbox:/home/postgres/ [pgxxx] alias u
alias u='dmk-run.pl'
postgres@pgbox:/home/postgres/ [pgxxx] alias ser
alias ser='dmk-run.pl -l y'
```

1. Display the PostgreSQL installation binary path, instead of PGDATA:

```
postgres@pgbox:/home/postgres/ [pgxxx] dmk-run.pl -d PGBIN


 PostgreSQL Clusters up and running on this host: 
 ---------------------------------------------------------------------------------------------- 
    pgdev       ->  /u01/app/postgres/product/DEV/db_0/                      ->  5432  ==> OPEN     
 
 PostgreSQL Clusters NOT running on this host: 
 ---------------------------------------------------------------------------------------------- 
    pg94        ->  /u01/app/postgres/product/9.4/db_26                      ->  3998  ==> CLOSED       
    pg95        ->  /u01/app/postgres/product/9.5/db_25                      ->  3999  ==> CLOSED       
    pg96        ->  /u01/app/postgres/product/9.6/db_24                      ->  4000  ==> CLOSED       
    pg10        ->  /u01/app/postgres/product/10/db_23                       ->  4001  ==> CLOSED       
    pg11        ->  /u01/app/postgres/product/11/db_22                       ->  4002  ==> CLOSED       
    pg12        ->  /u01/app/postgres/product/12/db_18                       ->  4003  ==> CLOSED       
    pg13        ->  /u01/app/postgres/product/13/db_14                       ->  4004  ==> CLOSED       
    pg14        ->  /u01/app/postgres/product/14/db_11                       ->  4005  ==> CLOSED       
    pg15        ->  /u01/app/postgres/product/15/db_6                        ->  4006  ==> CLOSED       
    pg16        ->  /u01/app/postgres/product/16/db_2                        ->  4007  ==> CLOSED    
```

2. Display a cluster's startup time

```
postgres@pgbox:/home/postgres/ [pgxxx] dmk-run.pl -s y


 PostgreSQL Clusters up and running on this host: 
 ---------------------------------------------------------------------------------------------- 
    pgdev       ->  /u02/pgdata/PGDEV                                        ->  5432  ==> OPEN     
                     Startup Time: 13-MAY-2024 07:46:49                                             
 
 PostgreSQL Clusters NOT running on this host: 
 ---------------------------------------------------------------------------------------------- 
    pg94        ->  /u02/pgdata/94                                           ->  3998  ==> CLOSED       
    pg95        ->  /u02/pgdata/95                                           ->  3999  ==> CLOSED       
    pg96        ->  /u02/pgdata/96                                           ->  4000  ==> CLOSED       
    pg10        ->  /u02/pgdata/10                                           ->  4001  ==> CLOSED       
    pg11        ->  /u02/pgdata/11                                           ->  4002  ==> CLOSED       
    pg12        ->  /u02/pgdata/12                                           ->  4003  ==> CLOSED       
    pg13        ->  /u02/pgdata/13                                           ->  4004  ==> CLOSED       
    pg14        ->  /u02/pgdata/14                                           ->  4005  ==> CLOSED       
    pg15        ->  /u02/pgdata/15                                           ->  4006  ==> CLOSED       
    pg16        ->  /u02/pgdata/16                                           ->  4007  ==> CLOSED       
```

#### Fixes

**Release 2.1.3**

* Add build instructions for Meson
* Add SSL related parameters to our Patroni template
* Add Meson and Ninja to the package lists

**Release 2.1.2**

* Update the documentation and release notes

**Release 2.1.1**

* Ensure that the environment variable PGBASE is set before PATH
* Ensure that PGBASE is also set when an PostgreSQL alias is set


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dbi-services.gitbook.io/dmk-postgresql-manual/release-notes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
