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.
Created by
brew bumpCreated with
brew bump-formula-pr.release notes
For sql-server instances with many databases, many branches or many tables and indexes, flushing stats could cause queries to block until stats were finished flushing. StatsController attempted to rate limited how much I/O bandwidth would be used to flush stats, but this is currently counter-productive because all queries are blocked from analyzing successfully until stats are flushed.
This changes it back to flush stats to disk as quickly as possible when we need to do it. Computing stats is already rate limited, so for large flushes this should not happen too often.
We will continue to improve things here so that stats writes have less impact on server resource utilization and do not block user-facing work as they proceed.
MutableMaps are designed for caching point modifications to a table. But during merge, the new primary index is computed sequentially. There's no benefit to using a MutableMap here.
MutableMaps are built on top of the
ApplyMutationsfunction, which takes a sequential stream of modifications (called a PatchBuffer) and applies them to a chunker. This has the added benefit of being parallelizable: the patches are produced in one goroutine and consumed in another.Instead of using the MutableMap, we can extract the underlying PatchBuffer and use it directly. This should be both more performant, and more correct as it avoids a failure case with schema merges where the MutableMap flushes changes to disk and writes a chunk containing rows with different schemas.
go-mysql-server
In MySQL non null enum columns default to the very first enum instead of throwing a missing default error.
fixes: INSERT to ENUM column with NOT NULL errors dolthub/dolt#8617
fixes: Error in
DESCRIBE PLAN SELECT COUNT(*) FROM tableon running server dolthub/dolt#8882The grouping key wasn't getting created correctly for DoltgresTypes, since they implement
sql.StringType, but aren't supported in GMS'types.ConvertToStringfunction. Tests for grouping with DoltgresTypes added in Doltgres.GROUP BYs andWINDOWs inINSERTandREPLACEstatements inTRIGGERSUsing aggregation and window functions inside a select statement inside an insert source inside a trigger was causing problems. For example, a trigger defined like so:
Projectionsover theGroup Bys. The scope for thegroup bys already contained the trigger's columns and are indexed uniquely, so we shouldn't include the trigger/parent scope.Closed Issues
DESCRIBE PLAN SELECT COUNT(*) FROM tableon running serverPREPARE/EXECUTEin stored procedures is buggycallof a stored procedure that uses session user variable always return NULL