repmgr
repmgr copied to clipboard
Changed v14 package name in install example
Per comment from Ton Machielsen in docs Slack channel: https://edb.slack.com/archives/CU5QEU5L7/p1669116950090219
I think this really depends on which repo they are using. Does our documentation specify a particular repository?
See output from dnf
:
$ dnf list repmgr* --disablerepo=edb,2ndquadrant-dl-default-release-pg12*
Last metadata expiration check: 1:56:28 ago on Tue 22 Nov 2022 03:07:33 PM UTC.
Available Packages
repmgr10.x86_64 5.2.0-1.rhel8 pgdg10
repmgr11.x86_64 5.2.0-1.rhel8 pgdg11
repmgr11-devel.x86_64 5.2.0-1.rhel8 pgdg11
repmgr12.x86_64 5.2.0-1.rhel8 pgdg12
repmgr12-devel.x86_64 5.2.0-1.rhel8 pgdg12
repmgr13.x86_64 5.2.0-1.rhel8 pgdg13
repmgr13-devel.x86_64 5.2.0-1.rhel8 pgdg13
repmgr_10.x86_64 5.3.2-1.rhel8 pgdg10
repmgr_11.x86_64 5.3.3-1.rhel8 pgdg11
repmgr_11-devel.x86_64 5.3.3-1.rhel8 pgdg11
repmgr_11-llvmjit.x86_64 5.3.3-1.rhel8 pgdg11
repmgr_12.x86_64 5.3.3-1.rhel8 pgdg12
repmgr_12-devel.x86_64 5.3.3-1.rhel8 pgdg12
repmgr_12-llvmjit.x86_64 5.3.3-1.rhel8 pgdg12
repmgr_13.x86_64 5.3.3-1.rhel8 pgdg13
repmgr_13-devel.x86_64 5.3.3-1.rhel8 pgdg13
repmgr_13-llvmjit.x86_64 5.3.3-1.rhel8 pgdg13
repmgr_14.x86_64 5.3.3-1.rhel8 pgdg14
repmgr_14-devel.x86_64 5.3.3-1.rhel8 pgdg14
repmgr_14-llvmjit.x86_64 5.3.3-1.rhel8 pgdg14
and
$ dnf list repmgr* --disablerepo=pgdg*,2ndquadrant-dl-default-release-pg12*
Last metadata expiration check: 1:58:22 ago on Tue 22 Nov 2022 03:06:19 PM UTC.
Available Packages
repmgr10.x86_64 5.3.0-1.el8 edb
repmgr10-debugsource.x86_64 5.3.2-1.el8 edb
repmgr11.x86_64 5.3.0-1.el8 edb
repmgr11-debugsource.x86_64 5.3.2-1.el8 edb
repmgr12.x86_64 5.3.0-1.el8 edb
repmgr12-debugsource.x86_64 5.3.2-1.el8 edb
repmgr13.x86_64 5.3.0-1.el8 edb
repmgr13-debugsource.x86_64 5.3.2-1.el8 edb
repmgr14.x86_64 5.3.0-1.el8 edb
repmgr14-debugsource.x86_64 5.3.2-1.el8 edb
repmgr96.x86_64 5.2.1-1.el8 edb
repmgr96-debugsource.x86_64 5.3.2-1.el8 edb
@kelpoole what do you think about this?
I suggest adding a note clarifying the divergence in package names in the PGDG yum repository (which wasn't our decision); the EDB package name format remains the same as a change would impact various internal tooling etc..