The same document states that "repmgr 5.5.0 is compatible with all
supported PostgreSQL versions from 13.x", so 12 shouldn't be listed in
the matrix.
Moreover, 14 is missing in 5.5 and 5.4.1, which looks like an accidental
omission that might have happened when support for 15 was added on a
version that only advertized 13 up to that point. 14 should have been
added along with 15 then.
When a t_node_info struct must be re initilised, it was re-declared
only. Moreover, a macro was user for any var creation of this type
impeding use the same to reset the values later if needed.
This new function allows to re initilise again a t_node_info typed
variable without the need to redeclare it to create other varibles for
the same purpose, and also shadowing is now avoided from pg16.
Macros seems to be replaced by `static inline` functions in upstream
postgres, credits to Alvaro Herrera <alvherre@alvh.no-ip.org> for this
idea.
References: HL-40
Since b5934bfd6071 in postgresql.git the flag
`-Wshadow=compatible-local` is activated. This commit fixes any
duplicated declaration made in the same function.
References: HL-40
Commit f69485c0 introduced a change in how we check if the repmgr
user can run checkpoints on PG15 and newer.
There was a regression in the messages where the conn passed
was not declared. That is because the pointer we were using was
called local_conn instead of conn.
Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>
Co-authored-by: Mario Gonzalez <mario.gonzalez@enterprisedb.com>
* Added check for pg_checkpoint role presence
This commit provides the needed infrastructure in `repmgr` so if the `repmgr` database
user is a member of the `pg_checkpoint` role, and inherits its privileges, there is no
need for such a user to be a superuser.
Co-authored-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>
