Ian Barwick
5e75707d4e
doc: clarify failover behaviour when node priority is zero
...
Make it clear the node will not be promoted under any circumstances.
2022-09-20 09:36:25 +09:00
Ian Barwick
8e5698f16e
repmgrd: ensure notification script is called for "repmgrd_upstream_disconnect"
...
GitHUb #760 .
2022-09-02 17:20:13 +09:00
Ian Barwick
3d08800521
doc: update note about pg_rewind corner-case bug
...
Sadly it's likely there are still installations running PostgreSQL
versions released prior to February 2021, so keep the note there
for now.
2022-07-14 10:18:25 +09:00
Ian Barwick
e64184aff3
doc: mention full_page_writes as prerequisite for pg_rewind
...
Anyone disabling it needs to examine their life choices, but as
we check for it anyway, might as well explicitly mention it for
completeness.
2022-07-14 09:49:03 +09:00
Ian Barwick
8c031e2b05
Replace some appendPQExpBuffer occurrences with appendPQExpBufferStr
2022-07-14 09:15:56 +09:00
Ian Barwick
3a157465ce
repmgr: update README
...
- update current version
- remove reference to upgrading from 3.x
2022-07-06 09:40:13 +09:00
Ian Barwick
70da9e8a53
Update Makefile
...
Re-add $(LIBS), previously removed in 9d7eebef .
While not required for internal builds, per GitHub #755 this may be
required in some environments.
2022-06-03 10:28:12 +09:00
Ian Barwick
6602a98f2e
doc: clarifications for upgrade process
2022-05-26 10:17:32 +09:00
Ian Barwick
b6ba0c3d45
Finalize 5.3.2 release
v5.3.2epas
v5.3.2
2022-05-25 15:59:51 +09:00
Ian Barwick
e4d6e2cd11
Add 5.3.2 release date
2022-05-25 14:03:04 +09:00
Ian Barwick
a28b6641b8
doc: update release notes
2022-05-25 14:01:51 +09:00
Ian Barwick
78d2acf204
doc: update release notes
2022-05-25 13:56:59 +09:00
Ian Barwick
b3d52c4332
shared library: remove redundant code
...
This has never actually served any purpose; see core commit ab02d702ef.
2022-05-17 19:56:48 +09:00
Ian Barwick
72ae977d0d
Bump version number
...
5.3.2
2022-05-17 09:38:40 +09:00
Ian Barwick
599351eea8
Ensure replication slots can be dropped by a replication-only user
...
If the repmgr user is a non-superuser, and a replication-only user exists,
ensure redundant replication slots are dropped correctly.
2022-05-16 16:38:02 +09:00
Ian Barwick
fca2b3ade7
doc: update release notes
2022-05-16 12:05:55 +09:00
Ian Barwick
89ba005726
repmgrd: improve walsender disable check
...
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.
2022-05-16 11:53:15 +09:00
Ian Barwick
5ddf450919
dbutils: move get_wal_receiver_pid() to a more consistent location
2022-05-16 10:41:31 +09:00
Ian Barwick
20342bb8ee
doc: expand non-superuser permissions explanation
...
Information about using repmgr with a non-superuser was spread
throughout individual documentation systems; this commit creates
an overview of requirements and potential issues.
2022-05-13 14:30:09 +09:00
Ian Barwick
ea36c5dde3
doc: clarify permissions requirements in "standby switchover"
2022-05-13 14:26:50 +09:00
Ian Barwick
fc72e0bf93
doc: clarify permissions requirements in "standby clone"
2022-05-13 14:26:44 +09:00
Ian Barwick
b10e9b89dd
standby clone: update source comment
2022-05-13 13:39:23 +09:00
Ian Barwick
a7d87d5992
doc: add missing short form option to "standby clone"
2022-05-13 11:56:06 +09:00
Ian Barwick
015c0c8458
dbutils.c: fix typo in comment
2022-05-13 11:56:02 +09:00
Ian Barwick
474d85d647
repmgr: fix error message
...
It's possible the missing node record might be for a witness server,
though we have no way of knowing that.
2022-05-11 14:57:34 +09:00
zhouhj43183
207057a159
repmgrd: ensure witness node marked active
...
Previously, if the witness node's PostgreSQL was unreachable, it would
be marked as "inactive" on the primary, and under some circumstances
would not be corrected to "active" once the witness node's PostgreSQL
came back.
PR #754 ; some modifications by Ian Barwick.
2022-05-11 13:36:46 +09:00
Ian Barwick
65d796ee3e
doc: update release notes
...
Add notes about when PostgreSQL and/or repmgrd restart required.
GitHub #752 .
2022-05-10 16:23:50 +09:00
Ian Barwick
0fb4c0930a
doc: update release notes
2022-05-10 16:09:46 +09:00
Ian Barwick
cee3b8446a
standby clone: don't error out if unable to determine cluster size
...
The cluster size check is purely informative, and is not in any way
essential for the standby clone operation. As it's possible the query
may fail if the repmgr user does not have sufficient privileges to
query all databases in the cluster, we can simply ignore any failure.
Note that the code comment indicated the query also served to sanity-
check that queries can actually be executed. While this was the case
historically, the preceding server version check now serves the same
purpose and will not have the same risk of failure due to missing
permissions.
2022-05-10 15:08:57 +09:00
Ian Barwick
90a700c7c0
node check: prevent WARNING in --downstream --nagios output
2022-04-20 17:46:39 +09:00
Ian Barwick
cc4475b8e2
node check: fix --downstream --nagios output
...
Ensure the performance data output (the bit after the pipe) contains
information in a pareseable format.
GitHub #749 .
2022-04-20 17:46:34 +09:00
Ian Barwick
9f1c9ef829
node check: tweak --upstream --nagios output
...
No data follows the pipe, so omit it and add missing line break.
2022-04-20 17:46:27 +09:00
Ian Barwick
2a05f495f6
doc: fix XML error
2022-04-19 11:26:01 +09:00
Felix Dreissig
d342acfefe
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:09:26 +09:00
Felix Dreissig
2f27fec510
Sample config: Update link to docs
2022-04-19 11:09:21 +09:00
James Stroud
a80ee17b6c
Update install-packages.xml postgres 14 and not 11
...
Hi, I think you had a typo, you meant to say Postgres 14 and not 11. If am wrong just ignore, thanks and take care James Stroud
2022-03-31 16:03:41 +09:00
Ian Barwick
595494f8a1
doc: use "note" rather than "important"
2022-03-16 10:40:51 +09:00
Ian Barwick
3ca4c273fa
doc: update witness server notes
...
- clarify that a separate PostgreSQL instance is needed for each
witness server
- remove historical 3.x reference
2022-03-16 10:33:56 +09:00
Ian Barwick
41f0688f69
docs: update package installation instructions
...
- use "dnf" in place of "yum"
- mention Rocky Linux
- remove 9.6 examples
2022-03-11 10:30:02 +09:00
Ian Barwick
78be15b06c
docs: update one more instance of the company name
v5.3.1epas
2022-02-15 16:21:43 +09:00
Ian Barwick
f02be50118
docs: update other instances of the company name, where appropriate
2022-02-15 16:14:31 +09:00
Ian Barwick
ac62101dc0
docs: update company name on cover pages
2022-02-15 16:01:51 +09:00
Ian Barwick
78cc278639
docs: finalize release notes
v5.3.1
v5.3.1rc1
2022-02-15 13:38:24 +09:00
Ian Barwick
ceb65027c6
Bump version number
2022-02-04 09:08:04 +09:00
Ian Barwick
e6caa14ea2
Bump version number
...
5.3.1
2022-02-03 14:48:47 +09:00
Ian Barwick
88a11f36ca
Add include for pwd.h
...
This was previously included via the PostgreSQL source, but that
seems to have gone away in recent HEAD builds.
2022-02-03 14:32:18 +09:00
Ian Barwick
7f371b11a5
doc: update version matrix
...
5.2.1 is the latest release in the 5.2.x series.
2022-02-03 13:30:29 +09:00
Ian Barwick
349eacd4b7
doc: update release notes
2022-02-03 13:29:32 +09:00
Ian Barwick
9f2afe9643
Fix upgrade paths from 4.1 ~ 4.3 to 5.2 and later
...
A number of C functions were added in releases 4.2 to 4.4; however
these were renamed in 5.3 to prevent naming clashes with other
extensions.
This does however mean that when upgrading from one of the above
versions, the intermediate upgrade steps will attempt to create
SQL functions referencing C functions which no longer exist in
repmgr.so, and hence cause the upgrade to fail.
We can work around this by providing empty upgrade scripts
from these versions to 4.4, which skip the problematic CREATE
FUNCTION commands. The functions will be correctly created in
the 5.2--5.3 upgrade script.
2022-02-03 13:29:25 +09:00
Ian Barwick
356f65531f
repmgrd: move connection pointer declaration inside relevant block
...
As it's used only there and nowhere else.
2022-01-04 12:46:50 +09:00