43b8a5f65f
Various improvements and fixes to the pg-backup-api restore section on the docs
...
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 >
2023-03-14 11:39:22 +01:00
26cfb56170
New sect2 block has to be inside the sect1. The closing tag has to go at the end.
...
Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com >
2023-03-14 10:14:16 +01:00
f0cc225de0
Adding new mode to clone standbys.
...
repmgr v5.4.0 supports this new mode called `pg_backupapi` which is
enabled by defining `pg_backupapi_host` in repmgr.conf.
2023-03-13 11:03:02 -03:00
8119aef378
Doc: Update or remove references to recovery.conf
...
The recovery.conf file is not present anymore for Postgres >= 12.
PR 748.
2022-04-19 11:06:08 +09:00
c6f137d438
docs: update other instances of the company name, where appropriate
2022-02-15 17:25:07 +09:00
842c67ca18
doc: various spelling fixes
...
Via GitHub #687 .
2020-12-22 13:47:56 +09:00
4b524c52b6
standby clone: honour --waldir setting when cloning from Barman
...
By setting --waldir in "pg_basebackup_options", standbys cloned using
pg_basebackup would have their WAL directory set to the specified
location and symlinked from the data directory.
This commit causes repmgr to honour that setting even when cloning
from Barman.
2020-10-07 15:13:52 +09:00
1131e3aad2
PostgreSQL 13: support "wal_keep_size"
...
Renamed from "wal_keep_segments" in core commit f5dff459.
2020-08-31 17:18:41 +09:00
ddde31b14e
doc: update section about passwords when cloning standbys
...
Reference new password management section and remove duplicate
info.
2020-03-18 17:24:39 +09:00
b3c09c48bf
doc: document "tablespace_mapping" parameter.
...
This was previously only mentioned in "repmgr.conf.sample".
2019-11-20 16:52:35 +09:00
c3aba173ea
doc: clarify Barman configuation
...
Per confusion noted in GitHub #602 .
2019-11-07 14:26:57 +09:00
93acdcfda2
doc: add single quotes to "barman_config" example.
...
Mandatory from repmgr 5.x.
2019-11-07 14:23:04 +09:00
b74f965f54
standby clone: rename --recovery-conf-only to --replication-conf-only
...
A more generic option name to cover pre- and post-Pg12 replication
configuration methods.
--recovery-conf-only is retained as an alias for backwards
compatibility.
2019-10-18 14:44:57 +09:00
cfc5bde219
doc: update repmgr.conf samples in Barman section
...
From repmgr 5.x we really need to quote all the things.
2019-10-07 12:05:26 +09:00
ea57269569
doc: improve instructions for cloning from Barman
2019-10-07 11:56:40 +09:00
e8b5b92893
doc: improve Barman standby clone example
2019-10-03 15:52:32 +09:00
405f70f769
doc: clarify barman-cli package usage
...
As of Barman 2.8, the barman-cli package has been merged with the core
Barman code, so is only requires an explicit mention for Barman 2.0 ~ 2.7.
2019-10-03 14:35:45 +09:00
577ca35de5
doc: remove reference to Barman 1.x.
...
Barman 1.x is very outdated and should no longer be used anyway.
2019-10-03 14:25:17 +09:00
215f4bb9d9
doc: add note about parallel restore from Barman
2019-07-18 09:23:09 +09:00
10425d6967
doc: rename file endings from .sgml to .xml
...
As they are now XML files. In PostgreSQL itself they remain with
the .sgml suffix for backwards compatibility, but that's not
important for us.
2019-05-20 15:38:40 +09:00
Martín Marqués