DuckDB v1.1.3 results #273
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
|
|
szarnyasg
force-pushed
the
duckdb-v1.1.3
branch
from
a0e1de9 to
2e17a31
Compare
szarnyasg
force-pushed
the
duckdb-v1.1.3
branch
from
1a89782 to
17ef036
Compare
|
@szarnyasg Thanks a lot for the update! Lgtm, merging. |
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.
Hi, Gabor here from DuckDB Labs. Here's a fresh set of DuckDB results with version 1.1.3 for
c6a.metalandc6.4xlargeinstances. I removed old resultsc5.4xlarge. Let me know if there are any changes required.