Assume custom time type range is same as bigint #2544
Merged
Conversation
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
Codecov Report
@@ Coverage Diff @@
## master #2544 +/- ##
==========================================
+ Coverage 90.06% 90.20% +0.13%
==========================================
Files 212 212
Lines 34228 34148 -80
==========================================
- Hits 30829 30802 -27
+ Misses 3399 3346 -53
Continue to review full report at Codecov.
|
erimatnor
force-pushed
the
fix-custom-time-types
branch
2 times, most recently
from
6ce70f2
to
e530418
Compare
erimatnor
force-pushed
the
fix-custom-time-types
branch
2 times, most recently
from
258ebc8
to
9a46609
Compare
|
There's an extra commit attached to this PR, which enhances functions for saturating subtraction and addition. Strictly, this could also be a separate PR if people feel strongly about this. |
mkindahl
reviewed
Oct 15, 2020
The database must know the valid time range of a custom time type, similar to how it knows the time ranges of officially supported time types. However, the only way to "know" the valid time range of a custom time type is to assume it is the same as the one of a supported time type. A previous commit tried to make such assumptions by finding an appropriate cast from the custom time type to a supported time type. However, this fails in case there are multiple casts available that each could return a different type and range. This change restricts the choice of valid time ranges to only that of the bigint time type. Fixes timescale#2523
Fix a check for a compatible chunk time interval type when creating a hypertable with a custom time type. Previously, the check allowed `Interval` type intervals for any dimension type that is not an integer type, including custom time types. The check is now changed so that it only accepts an `Interval` for timestamp and date type dimensions. A number of related error messages are also cleaned up so that they are more consistent and conform to the error style guide.
The functions for saturating addition and subtraction of time values assumed positive intervals as input. This change generalizes the code to also handle negative intervals being added or subtracted.
erimatnor
force-pushed
the
fix-custom-time-types
branch
from
9a46609
to
571b2c1
Compare
mkindahl
approved these changes
Oct 15, 2020
pmwkaa
approved these changes
Oct 15, 2020
svenklemm
approved these changes
Oct 15, 2020
svenklemm
added a commit
to svenklemm/timescaledb
that referenced
this pull request
Oct 20, 2020
This release candidate contains bugfixes since the previous release candidate. **Minor Features** * timescale#2520 Support non-transactional distibuted_exec **Bugfixes** * timescale#2307 Overflow handling for refresh policy with integer time * timescale#2503 Remove error for correct bootstrap of data node * timescale#2507 Fix validation logic when adding a new data node * timescale#2510 Fix outer join qual propagation * timescale#2514 Lock dimension slices when creating new chunk * timescale#2515 Add if_attached argument to detach_data_node() * timescale#2517 Fix member access within misaligned address in chunk_update_colstats * timescale#2525 Fix index creation on hypertables with dropped columns * timescale#2543 Pass correct status to lock_job * timescale#2544 Assume custom time type range is same as bigint * timescale#2563 Fix DecompressChunk path generation * timescale#2564 Improve continuous aggregate datatype handling * timescale#2568 Change use of ssl_dir GUC * timescale#2571 Make errors and messages conform to style guide
Merged
svenklemm
added a commit
to svenklemm/timescaledb
that referenced
this pull request
Oct 20, 2020
This release candidate contains bugfixes since the previous release candidate. **Minor Features** * timescale#2520 Support non-transactional distibuted_exec **Bugfixes** * timescale#2307 Overflow handling for refresh policy with integer time * timescale#2503 Remove error for correct bootstrap of data node * timescale#2507 Fix validation logic when adding a new data node * timescale#2510 Fix outer join qual propagation * timescale#2514 Lock dimension slices when creating new chunk * timescale#2515 Add if_attached argument to detach_data_node() * timescale#2517 Fix member access within misaligned address in chunk_update_colstats * timescale#2525 Fix index creation on hypertables with dropped columns * timescale#2543 Pass correct status to lock_job * timescale#2544 Assume custom time type range is same as bigint * timescale#2563 Fix DecompressChunk path generation * timescale#2564 Improve continuous aggregate datatype handling * timescale#2568 Change use of ssl_dir GUC * timescale#2571 Make errors and messages conform to style guide * timescale#2577 Exclude compressed chunks from ANALYZE/VACUUM
svenklemm
added a commit
to svenklemm/timescaledb
that referenced
this pull request
Oct 20, 2020
This release candidate contains bugfixes since the previous release candidate. **Minor Features** * timescale#2520 Support non-transactional distibuted_exec **Bugfixes** * timescale#2307 Overflow handling for refresh policy with integer time * timescale#2503 Remove error for correct bootstrap of data node * timescale#2507 Fix validation logic when adding a new data node * timescale#2510 Fix outer join qual propagation * timescale#2514 Lock dimension slices when creating new chunk * timescale#2515 Add if_attached argument to detach_data_node() * timescale#2517 Fix member access within misaligned address in chunk_update_colstats * timescale#2525 Fix index creation on hypertables with dropped columns * timescale#2543 Pass correct status to lock_job * timescale#2544 Assume custom time type range is same as bigint * timescale#2563 Fix DecompressChunk path generation * timescale#2564 Improve continuous aggregate datatype handling * timescale#2568 Change use of ssl_dir GUC * timescale#2571 Make errors and messages conform to style guide * timescale#2577 Exclude compressed chunks from ANALYZE/VACUUM
svenklemm
added a commit
that referenced
this pull request
Oct 20, 2020
This release candidate contains bugfixes since the previous release candidate. **Minor Features** * #2520 Support non-transactional distibuted_exec **Bugfixes** * #2307 Overflow handling for refresh policy with integer time * #2503 Remove error for correct bootstrap of data node * #2507 Fix validation logic when adding a new data node * #2510 Fix outer join qual propagation * #2514 Lock dimension slices when creating new chunk * #2515 Add if_attached argument to detach_data_node() * #2517 Fix member access within misaligned address in chunk_update_colstats * #2525 Fix index creation on hypertables with dropped columns * #2543 Pass correct status to lock_job * #2544 Assume custom time type range is same as bigint * #2563 Fix DecompressChunk path generation * #2564 Improve continuous aggregate datatype handling * #2568 Change use of ssl_dir GUC * #2571 Make errors and messages conform to style guide * #2577 Exclude compressed chunks from ANALYZE/VACUUM
svenklemm
added a commit
that referenced
this pull request
Oct 20, 2020
This release candidate contains bugfixes since the previous release candidate. **Minor Features** * #2520 Support non-transactional distibuted_exec **Bugfixes** * #2307 Overflow handling for refresh policy with integer time * #2503 Remove error for correct bootstrap of data node * #2507 Fix validation logic when adding a new data node * #2510 Fix outer join qual propagation * #2514 Lock dimension slices when creating new chunk * #2515 Add if_attached argument to detach_data_node() * #2517 Fix member access within misaligned address in chunk_update_colstats * #2525 Fix index creation on hypertables with dropped columns * #2543 Pass correct status to lock_job * #2544 Assume custom time type range is same as bigint * #2563 Fix DecompressChunk path generation * #2564 Improve continuous aggregate datatype handling * #2568 Change use of ssl_dir GUC * #2571 Make errors and messages conform to style guide * #2577 Exclude compressed chunks from ANALYZE/VACUUM
svenklemm
added a commit
that referenced
this pull request
Oct 20, 2020
This release candidate contains bugfixes since the previous release candidate. **Minor Features** * #2520 Support non-transactional distibuted_exec **Bugfixes** * #2307 Overflow handling for refresh policy with integer time * #2503 Remove error for correct bootstrap of data node * #2507 Fix validation logic when adding a new data node * #2510 Fix outer join qual propagation * #2514 Lock dimension slices when creating new chunk * #2515 Add if_attached argument to detach_data_node() * #2517 Fix member access within misaligned address in chunk_update_colstats * #2525 Fix index creation on hypertables with dropped columns * #2543 Pass correct status to lock_job * #2544 Assume custom time type range is same as bigint * #2563 Fix DecompressChunk path generation * #2564 Improve continuous aggregate datatype handling * #2568 Change use of ssl_dir GUC * #2571 Make errors and messages conform to style guide * #2577 Exclude compressed chunks from ANALYZE/VACUUM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The database must know the valid time range of a custom time type,
similar to how it knows the time ranges of officially supported time
types. However, the only way to "know" the valid time range of a
custom time type is to assume it is the same as the one of a supported
time type.
A previous commit tried to make such assumptions by finding an
appropriate cast from the custom time type to a supported time
type. However, this fails in case there are multiple casts available
that each could return a different type and range.
This change restricts the choice of valid time ranges to only that of
the bigint time type.
Fixes #2523