Skip to content

Releases: cybertec-postgresql/pgwatch2

v1.12.0

28 Dec 10:28
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.11.0...v1.12.0

v1.11.0

21 Aug 09:41
738cf43
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.10.0...v1.11.0

v1.10.0

08 Feb 12:14
5266078
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.9.0...v1.10.0

v1.9.0

25 Apr 12:41
a0c5462
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.8.5...v1.9.0

v1.8.5

03 May 16:05
Compare
Choose a tag to compare

See the list of major changes here.

NB! No schema migration diffs to be applied for older Config DB based installations.

NB2! For file-based DEB / RPM installations starting from this release also metric definitions are considered as config files to avoid transparently overriding custom metric changes done by user. Thus when upgrading you might get quite many annoying confirmation dialogs. If you're sure that you have not changed anything then one can bypass them by: a) using some force flag like --force-confnew with dpkg b) purging the older package version c) deleting the /etc/pgwatch2/metrics/ contents. In the first two cases make sure though to back up the monitored instances configuration file, located at /etc/pgwatch2/config/instances.yaml by default.

v1.8.4

12 Feb 08:21
Compare
Choose a tag to compare

See list of major changes here.

v1.8.3

23 Dec 10:50
Compare
Choose a tag to compare

There is only 1 change in this minor release compared to the previous v1.8.2, fixing hopefully finally the issue with unnecessary internal worker restarts, causing much higher storage usage on the metrics DB.

NB! Please do not use the v1.8.2 version!!!

v1.8.2

22 Dec 14:35
Compare
Choose a tag to compare

See list of major changes here.

This release added 1 SQL diff to be applied to Config DB based setups to support the new optional Patroni "namespace discovery" feature.

Also it is always highly recommended to refresh the metric definitions separately if using a config DB based setup.

v1.8.1

22 Oct 11:25
Compare
Choose a tag to compare

See list of major changes here.

This release added 1 SQL diff to be applied for Config DB based setups to support the new optional "Standby configuration" feature.

Also it is highly recommended to refresh the metric definitions if using a config DB based setup.

v1.8.0

10 Jul 15:56
Compare
Choose a tag to compare

See list of major changes here.

NB! Config DB migrations are needed for this release if updating from pre v1.8.0 versions. This time also it is highly recommended to refresh the metric definitions (if using a config DB based setup).