-
Notifications
You must be signed in to change notification settings - Fork 916
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
Add a new dummy compression called NULL #7798
base: main
Are you sure you want to change the base?
Add a new dummy compression called NULL #7798
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #7798 +/- ##
==========================================
+ Coverage 80.06% 81.90% +1.83%
==========================================
Files 190 248 +58
Lines 37181 45531 +8350
Branches 9450 11393 +1943
==========================================
+ Hits 29770 37293 +7523
- Misses 2997 3749 +752
- Partials 4414 4489 +75 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
5e48616
to
ebd2b32
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.
Let's merge this w/o the ts_is_attribute_missing
, it's a separate function and I think we might want to improve it. The fix itself is fine.
0a129d7
to
899adf1
Compare
899adf1
to
7a2bc7e
Compare
faaa1da
to
d162f9c
Compare
This fixes bug timescale#7714 where adding a column with a default value (jargon: missing value) and a compressed batch with all nulls created an ambiguity. In the all null cases the compressed block was stored as a NULL value. With this change, I introduce a new special compression type, the 'NULL' compression which is a single byte place holder for an 'all-null' compressed block. This allows us to distinguish between the missing value vs the all-null values. Please note that the wrong results impacted existing tests so I updated the expected results, as well as I added reference queries before compression to prove the updated values were wrong before. A new debug only GUC was added for testing a future upgrade script, which will arrive as a separate PR. Fixes timescale#7714
d162f9c
to
977c85b
Compare
This fixes bug #7714 where adding a column with a default value (jargon: missing value) and a compressed batch with all nulls created an ambiguity. In the all null cases the compressed block was stored as a NULL value.
With this change, I introduce a new special compression type, the 'NULL' compression which is a single byte place holder for an 'all-null' compressed block. This allows us to distinguish between the missing value vs the all-null values.
Please note that the wrong results impacted existing tests so I updated the expected results, as well as I added reference queries before compression to prove the updated values were wrong before.
A new debug only GUC was added for testing a future upgrade script, which will arrive as a separate PR.
Fixes #7714