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 1.4.2 #1430
Release 1.4.2 #1430
Conversation
CHANGELOG.md
Outdated
@@ -13,7 +21,6 @@ accidentally triggering the load of a previous DB version.** | |||
* #1408 Fix ChunkAppend space partitioning support for ordered append | |||
* #1420 Fix OUTER JOIN qual propagation | |||
* #1422 Fix background worker segfaults |
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.
Is 1423 going in 1.4.2 or not? If so, should the notes be updated to say "release address one potential segfault" instead of 2?
Also, might be nice to have bugfix description point out where segfault happens in consistent manner so you can scan, which we can use going forward in our release notes:
e.g., Fix background worker SOMETHIGN (potential segfault)
and Fix SOMETHING on ARM/32-bit builds (potential segfault).
Otherwise, LGTM.
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 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.
Sounds good. I would then just reiterate that it would be a good thing to have bufgfix description mention that, e.g., #1392 Fix cagg_agg_validate expression handling (potential segfault)
I think this is useful when readers see the notes to determine whether upgrade is important for them, i.e., if they aren't using cagg or are ARM32, then nothing here is a segfault.
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.
LGTM other than Mike's comment
12734e3
to
26a9738
Compare
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.
Looks good from my end
26a9738
to
82b3d67
Compare
Codecov Report
@@ Coverage Diff @@
## master #1430 +/- ##
==========================================
- Coverage 90.19% 81.23% -8.97%
==========================================
Files 116 116
Lines 17471 16763 -708
==========================================
- Hits 15758 13617 -2141
- Misses 1713 3146 +1433
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #1430 +/- ##
==========================================
- Coverage 90.19% 81.22% -8.98%
==========================================
Files 116 116
Lines 17471 16763 -708
==========================================
- Hits 15758 13615 -2143
- Misses 1713 3148 +1435
Continue to review full report at Codecov.
|
This maintenance release contains bugfixes since the 1.4.1 release. We deem it medium priority for upgrading. In particular the fixes contained in this maintenance release address 2 potential segfaults and no other security vulnerabilities. The bugfixes are related to background workers, OUTER JOINs, ordered append on space partitioned hypertables and expression indexes.
82b3d67
to
5199146
Compare
This maintenance release contains bugfixes since the 1.4.1 release. We deem it medium
priority for upgrading.
In particular the fixes contained in this maintenance release address 2 potential
segfaults and no other security vulnerabilities. The bugfixes are related to
background workers, OUTER JOINs, ordered append on space partitioned hypertables
and expression indexes.