We've done extensive testing of the current version of repmgr against the
new version 16 of Postgres. The tests have passed which gives us the
green light to add the version as supported in repmgr 5.4.1.
The commit only addresses documentation amendments
Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>
This release contains all changes related to the new pg-backupapi mode
along with the related documentation. In the previous release, we didn't
include any documentation at all, just the required C code.
This release added support for pg-backup-api. Here we add the
release notes which expose the new feature.
Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>
I added a paragraph at the beginning of the section on where to look for
instructions on how to install the pg-backup-api rest API.
Fixed typos and some gramatical changes. Also reworded the first paragraph
(which is now the second one).
Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>
If the primary changed while the witness repmgrd was not running,
ensure the witness's upstream node ID is updated when the witness
repmgrd is restarted.
This release added support for pg-backup-api. Here we add the
release notes which expose the new feature.
Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>
I added a paragraph at the beginning of the section on where to look for
instructions on how to install the pg-backup-api rest API.
Fixed typos and some gramatical changes. Also reworded the first paragraph
(which is now the second one).
Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>
Module to provide communication with a server in order to send new
tasks and query them.
pg-backup-api is a REST api that at the moment, is integrated with
barman only, and can provide a communication interface in order to
perform remote recoveries through background tasks. There are cases
where instead of writing a new repmgr module of some feature that
exists in backup tools already, like barman, pg-backup-api can
provide that integration.
Sonarqube has been failing for some time (seems like a user/credential
problem).
There will be discussion on how we'll resolve this, but that will be
sometime in the future. For now we are just removing the action.
Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>
We are checking for sed amd other external tools inside configure script,
now is turn of flex.
In systems without flex you will have this error:
gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement
[...]
postgresql/internal -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/libxml2 -c -o configfile.o configfile.c
flex -o'configfile-scan.c' configfile-scan.l
make: flex: No such file or directory
make: *** [Makefile.global:40: configfile-scan.c] Error 127
Fixed a mising closing quote and closing parenthesis in the repmgrd overview
section of the documentation.
Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>
Anyone still using PostgreSQL 9.4 should re-examine their life choices
at this point, but as it is not yet de-supported by repmgr, consolidate
the references to it whenever pg_rewind is mentioned to a single
section.
Specifically, don't attempt to disable walsenders if "standby_disconnect_on_failover"
is "true", but the repmgr user is not a superuser.
This restriction can be lifted from PostgreSQL 15.
