pgwatch v4? Yes, after a long time of silence, we are finally releasing a new major version!
Table of Contents
What happened to pgwatch v3!? It was released less than a year ago!
If Firefox can have version 142 and Chrome version 139 (and those numbers are probably already outdated by the time of publishing), why should we care about strict versioning? 🙂
On a more serious note, we decided to stick to the PostgreSQL major versioning scheme, so pgwatch major releases will now follow PostgreSQL major releases.
Why not pgwatch v18 then? Because we are not that ambitious. 🙂
But seriously, we don't want to confuse users by signaling that the new pgwatch will only work with the latest PostgreSQL version, as this is not the case. Plus, pgwatch supports all PostgreSQL forks (like Greenplum, Amazon Aurora, etc.) and poolers, pgBackRest, and so on, and so forth. The imagination is the only limitation here!
TL;DR: You can see it in action on demo.pgwatch.com.
And you can check the detailed changelog on Github.
Screenshots worth a thousand words:
- 🎁 New gRPC Sink (GSoC 2025 project) allows you to build a custom measurement storage and/or analytic layer;
- 🔐 Added basic auth support
- 📘 Added documentation
- 🔄 Improved error handling (don't fail on DB resolve, skip on COPY failure)
- 📂 Metrics can be loaded from a folder that gives the user more control over metric definitions;
- 📑 Sample metrics YAML file included;
- ⚡ Improved change_events metric processing with lower memory usage;
- 📝 Documentation updates & clarifications!
We plan on releasing pgwatch v4 stable in a few weeks, in parallel with the PostgreSQL v18 release.
If you want to discuss pgwatch in person, you can meet us at PostgreSQL Conference Europe 2025
in Riga, Latvia.
Or drop a line on our GitHub Discussions. Of course, do not forget to star the project on GitHub.
And do not hesitate to open Pull Requests if you want to contribute!
Happy monitoring! 💙💛
Leave a Reply