Trusted Postgres Architect 23.40.1 release notes v23.40.0

In a PGD-AlwaysON cluster with a BDR node that is also a physical replica, the upgrade process would fail during the alter_node_option task because a BDR node is expected to have RAFT enabled, but the physical replica BDR node does not. TPA now skips this task on any node with the replica role, allowing upgrade to complete successfully.

TPA recently relocated the pgbouncer_auth_function used to authenticate users when pgbouncer is in use. This was done in an effort to better follow the best practices and avoid issues during upgrade where pg_catalog function would not be part of the dump of the database. TPA introduced a post deploy check to help users still relying on the auth function defined in pg_catalog to identify the problem and make sure that they are able to fix it before removing the function from their systems. This check was used as a transition mechanism and is now being removed. This resolves issues with unwanted output generated by that check.

Previously, when using the backup_name variable, TPA would incorrectly use this name in pgpass for the Barman server. This has been fixed and the documentation has been updated.

TPA can deploy the Beacon Agent to monitor the health of a system. However, it needs access to a valid EDB repository. This change ensures that the Standard repository is enabled when the Beacon Agent is to be deployed.

When setting up a barman node, the variable 'barman_log_file' was not setting up an alternative directory to place the log file. Instead, it used the default location (/var/log/barman/barman.log). Bug and fix reported by voxnyx (https://github.com/voxnyx).