23569a19b1
Doc fix: PostgreSQL 9.4 is no longer considered recent
2019-02-25 13:02:56 +09:00
4523137bfc
doc: note "pg_read_all_settings" in FAQ
...
Relevant for PostgreSQL 10 and later where the repmgr user is not a superuser.
2019-01-16 11:27:35 +09:00
666f5cf851
doc: add FAQ entry clarifying why "data_directory" is required in repmgr.conf
2019-01-16 09:50:29 +09:00
ba7ef9e643
doc: update PostgreSQL documentation links
...
"/static/" path element no longer required.
2019-01-15 12:45:33 +09:00
40410e43ab
doc: update FAQ
...
Make it clear 3.x is no longer maintained.
2019-01-07 12:34:43 +09:00
3c25d5a03a
doc: update FAQ
...
Add link to repmgr compatibility matrix.
2019-01-07 12:22:52 +09:00
7e21ceb158
doc: note importance of installing same repmgr versions
2019-01-07 12:18:17 +09:00
b419c5fec7
doc: update FAQ
...
Emphasize that repmgr does not actually perform replication.
2018-11-05 10:06:43 +09:00
273db444b2
doc: clarify replication slot FAQ entry
2018-10-31 16:20:15 +09:00
2bf3eeb931
doc: update FAQ
...
Emphasize that repmgr does not actually perform replication.
2018-10-31 11:56:41 +09:00
b7d576863d
doc: update FAQ
...
Add note about why repmgrd refuses to start up if the upstream is
not running.
2018-08-20 15:33:55 +09:00
c1338df5e3
doc: clarify repmgrd FAQ item
...
"priority" must be 0 or greater.
2018-08-20 15:30:43 +09:00
987823861f
doc: document sources of old package versions
2018-08-20 15:25:00 +09:00
7bcf87b8ed
doc: update FAQ
...
Explain why some values in recovery.conf are surrounded by pairs of single
quotes.
2018-08-15 14:42:56 +09:00
f8667c1aac
doc: better explain where pg_bindir won't be applied
...
Basically any setting which can contain a user-defined script
*must* have the full path set, even if it's repmgr being executed.
We could potentially apply some heuristics to detect if the first
item in the setting is "repmgr" (or more precisely repmgrd's program
name), but this will require some careful thought and testing
that it works as intended.
2018-08-14 09:54:27 +09:00
a2ff1536ad
doc: add notes about package compatibility
...
We need to emphasise that the repmgr packages are only compatible
with packages based on the PGDG filesystem layout; 3rd party vendor
packages often put application and data directories elsewhere.
See e.g. GitHub #427 .
2018-05-10 10:38:54 +09:00
0dcddbb062
doc: minor FAQ tweaks
2018-04-05 17:10:33 +09:00
644a56a645
doc: miscelleneous FAQ updates
...
- clarify pg_rewind item
- add note about what's included in recovery.conf
2018-04-04 10:07:08 +09:00
ff0ba3e19a
doc: update FAQ
...
Additional clarification for "repmgr standby clone --recovery-conf-only"
2018-03-08 19:11:33 +09:00
6f5cce7e6f
doc: update FAQ
...
Add entry about upgrading PostgreSQL
2018-03-08 19:11:21 +09:00
15625183c1
"standby clone": document --recovery-conf-only option
2018-02-23 11:19:21 +09:00
9951a8e106
doc: add appendix with details about packages
...
work-in-progress
2018-01-02 17:23:24 +09:00
a9a17f206e
docs: improve documentation of pg_basebackup_options
2017-11-15 20:50:13 +09:00
7c3abe28b9
Standardize terminology on "primary" (in place of "master")
2017-10-24 13:42:50 +09:00
7bf3c78f57
Add 4.0 release notes
2017-10-19 13:58:41 +09:00
2745c92fc8
Documentation: update markup
2017-10-18 11:12:20 +09:00
91354a71cc
Add FAQ to documentation
2017-10-17 15:46:36 +09:00
John Naylor