| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| install.sh | 2025-12-19 | 3.4 kB | |
| doltgresql-windows-amd64.7z | 2025-12-19 | 26.0 MB | |
| doltgresql-windows-amd64.zip | 2025-12-19 | 44.6 MB | |
| doltgresql-darwin-arm64.tar.gz | 2025-12-19 | 44.1 MB | |
| doltgresql-darwin-amd64.tar.gz | 2025-12-19 | 46.6 MB | |
| doltgresql-linux-arm64.tar.gz | 2025-12-19 | 43.7 MB | |
| doltgresql-linux-amd64.tar.gz | 2025-12-19 | 47.3 MB | |
| 0.54.7 source code.tar.gz | 2025-12-18 | 11.9 MB | |
| 0.54.7 source code.zip | 2025-12-18 | 13.4 MB | |
| README.md | 2025-12-18 | 2.9 kB | |
| Totals: 10 Items | 277.6 MB | 2 | |
Merged PRs
doltgresql
- 2132: Fixed JSONB extended value error Fixes the issue:
- https://github.com/dolthub/doltgresql/issues/2127
- 2128: Added some hooks for DROP TABLE
This adds support for ensuring that dropping a table while using table types doesn't outright put the database in an unusable state. There are many more hooks that need to be implemented across the board, but these are relatively straightforward ones for a common case of dropping a table, function, or procedure that uses them.
This also adds support for
DROP PROCEDURE, which I apparently overlooked when adding procedure support in general. Lastly, this adds support for the serialization and deserialization of values within columns that use table types. While it was previously possible to create tables that use table types, it wasn't possible to read from those tables (and writing to them just wrote useless data that couldn't be removed). You'll notice that error messages involving procedures return "function" instead of "procedure". Postgres calls them functions in their error messages, so we're replicating that. - 2125: Changed configuration file for function passing
In a nutshell, our internal repository for handling Hosted Doltgres only needs to include the configuration file, however recent changes added more packages that were referenced from our
servercfgpackage. As our internal repository wasn't configured to handle these additional packages (which essentially requires building the entirety of Doltgres), it broke the existing workflow. To workaround this, I've moved the "details" of the configuration to its own package (namedcfgdetails), and that will be referenced by our internal repository. Elsewhere in Doltgres, we still refer toservercfg, which has a wrapper struct around our details. The wrapper is needed as we cannot store a field that contains the overrides on the struct itself. Our YAML deserialization function does not honor ignored fields (which are supposed to work usingyaml:"-") and is therefore panicking. Instead, the wrapper declares its ownOverrides()function that overrides the function withincfgdetails. - 2123: Bug fix: ensure OR expressions on a single table use an index when possible
This fixes the performance regression in select_random_ranges, which uses
BETWEEN .. OR BETWEEN ..in its filters. Requires https://github.com/dolthub/go-mysql-server/pull/3347