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 bump
Created with
brew bump-formula-pr
.release notes
dolt.status
,dolt.merge_status
anddolt_constraint_violations_*
Dolt PR: Add pointers for schemas for
dolt_workspace_*
anddolt_diff
system tables for doltgres dolthub/dolt#8634This reworks how functions are accessed within
DoltgresType
, in addition to adding a faster path for functions that fall under specific criteria.GMS: Add schema to StatsQualifier for schema databases dolthub/go-mysql-server#2762
Dolt: Fix dolt_statistics table for multiple schemas for doltgres dolthub/dolt#8589
to_char
for timestamp (mostly)This PR adds support for most of the date format specifiers mentioned here: https://www.postgresql.org/docs/current/functions-formatting.html
Dolt PR: Support per-schema dolt_ignore for doltgres dolthub/dolt#8581
Dolt PR: https://github.com/dolthub/dolt/pull/8578/files
This adds a new workflow that runs on every PR, similar to the regression tests. This runs a small version of the sysbench tests, primarily to detect large performance changes that a PR may unexpectedly introduce. For now, the variance is set to ±10%. That is, if it's under 10% in either direction, it'll just display as a white color. If it's greater, then it'll display as green or red respectively to indicate a possible performance regression. There's variability in the tests, that we'll want to account for, but perhaps the 10% window is too large. Or maybe we should run the tests for longer.
This reverts commit 40dba4f84d4cf7533ee5bb4a049131eb7b0d9edc, reversing changes made to 165c30e7f841e9e4b40015526f2c569b7605f994.
Reverting this change because of performance regression.
This adds a myriad of tests, in addition to:
There are also many smaller changes, such as disallowing non-superusers from modifying superusers, and many more.
DEFAULT VALUES
This is postgres special syntax that allows you to just insert all default values.
This is equivalent to
insert into <tbl> values ()
in MySQL.EXCEPT
set operationEXISTS
subqueryThis PR adds support for
EXISTS <subquery>
clause.Additionally, we have to add a bunch of skips namely in the setup queries in the
testing/go/regression/results
directory; these queries encounter performance issues for joins overpg_catalog
tables discussed here: Add caching forpg_catalog
tables dolthub/doltgresql#940partition of
queriesThese were panicking before, but now we throw unsupported
DEFAULT
insert forNULL
or unspecified column default valuesCreated by the Release workflow to update DoltgreSQL's version
with
somewhat related:
WITH
clause not support (needed to getdolt_blame_$tablename
working) dolthub/doltgresql#928This PR replaces current
DoltgresType
interface withDoltgresType
struct. All built-in types will have pre-defined values for this struct. User-defined types will populate the struct fields with appropriate values.Depends on use Equals method for sql.Types dolthub/go-mysql-server#2736
Closed Issues
#benchmark
so latency regressions can be caught before they're merged.statement_timeout