chore: Tighten and test min/max bounds for Arrow datetime tests#4465
Merged
chore: Tighten and test min/max bounds for Arrow datetime tests#4465
Conversation
## What Further narrow the min/max bounds of our Arrow + Postgres + Tantivy datetime tests, and ensure that the bound is covered. ## Why #4410 narrowed the bounds for these tests, but did not guarantee that the new values would be tested. Therefore, inevitably, the bounds were wrong! (cherry picked from commit dcc213b)
paradedb-bot
added
the
automated-cherry-pick
paradedb-bot
added
the
automated-cherry-pick
stuhood
approved these changes
Mar 24, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Backport of #4463 to
0.22.x.