Releases: vitabaks/pgbackrest_auto
Releases · vitabaks/pgbackrest_auto
v1.6.0
What's Changed
- allocate a free port before starting Postgres (not earlier) by @vitabaks in #13
- Increase the timeout for the pg_ctl start command by @vitabaks in #14
- Implement multithreading for database checks with pgbackrest_auto by @vitabaks in #18
- add '
process-max
' option - add multithreading to "
dummy-dump
" chek - add multithreading to "
amcheck
" chek
- add '
- Fix compatibility of "checksums" checks with Postgres 11 and older
Full Changelog: v1.5.0...v1.6.0
v1.5.0
new features
- Compatibility with Red Hat family Linux distributions (#8)
--custom_options
for support s3 repo-type and etc... (#9 thanks @artemsafiyulin )
improvements
- function amcheck: add heapallindexed (9bc5745)
fixes
v1.4.0
new features
- add monitoring with zabbix (#3) thanks @artemsafiyulin
-
- but if necessary, you can check the
status_file
by any monitoring system.
- but if necessary, you can check the
improvements
- code improvements for
pg_check_recovery()
andpgisready()
functions (#2) thanks @artemsafiyulin
v1.3.1
v1.3
- check data checksums with pg_checksums. "
--checksums
" (and "--checkdb
") option (requirespostgresql-<version>-pg-checksums
package for PostgreSQL version 11 and below) - "
--dummy-dump
" option. Verify that data can be read out. Check with pg_dump >> /dev/null - "
--amcheck
" option. Validate Indexes (verify the logical consistency of the structure of indexes and heap relations) - "
--norestore
" option to check already existing clusters - automatic determine Postgres version from pgbackrest info
- automatic create a new postgres cluster (initdb) to restore to the path specified in the "--to" option (if it does not exist)
- determine postgresql parameters from pg_controldata and configure postgresql.conf accordingly after restore
- compare DB and filesystem size before restore
- remove colors in log messages
- remove dependencies - gawk, ansi2html.sh
- a little code refactoring
v1.2: Bug Fix
Bug Fixes:
- [ae6cafd] The pg_logical_validation() function was creating the amcheck extension, but did not actually perform indexes checking with bt_index_parent_check for PostgreSQL version 11 or later.