-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 0.63.0 #638
Merged
Merged
Release 0.63.0 #638
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,24 @@ | ||
# Changelog | ||
|
||
## 0.63.0 2024-11-21 | ||
|
||
* Fix WebSocket error handling | ||
- If the WebSocket mechanism hit an error at the wrong time, this could cause | ||
a stuck collector state, where the collector would keep running but stop | ||
processing and sending snapshots | ||
* Track Postgres buffer cache usage | ||
- This reports statistics from [pg_buffercache](https://www.postgresql.org/docs/current/pgbuffercache.html) | ||
if available | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It might be good to mention the |
||
* Fix partitioned table stats handling | ||
- Partitioned table stats are now reported as aggregations over child partition stats | ||
* Add collector query runner | ||
- This provides a mechanism for the collector to help pganalyze users run | ||
EXPLAIN queries in future versions of pganalyze | ||
- This is disabled by default | ||
* Update packaging scripts to use the `groupadd` command instead of `addgroup` when installing | ||
- `addgroup` is not available on some newer distributions, e.g., Amazon Linux 2023 | ||
|
||
|
||
## 0.62.0 2024-11-13 | ||
|
||
* Fix PII filtering for detail log lines | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
package util | ||
|
||
const CollectorVersion = "0.62.0" | ||
const CollectorVersion = "0.62.1" | ||
const CollectorNameAndVersion = "pganalyze-collector " + CollectorVersion |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The version in the code was updated to 0.62.1, but this is 0.63.0?
If we want to do a patch release I'd assume it would branch off of the previous release instead of releasing the main branch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's probably no harm in going ahead and releasing 0.63.0. We're already running this version of the collector in production.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I started with 0.62.1 but then reviewing the changes, I realized this probably needs to be a 0.63.0. I fixed the code references now. We haven't done collector patch releases on older versions in the past, and I don't think it's worth doing it here.