Download Latest Version doltgresql-windows-amd64.7z (26.7 MB)
Email in envelope

Get an email when there's a new version of DoltgreSQL

Home / v0.56.1
Name Modified Size InfoDownloads / Week
Parent folder
install.sh 2026-04-08 3.4 kB
doltgresql-windows-amd64.7z 2026-04-08 26.7 MB
doltgresql-windows-amd64.zip 2026-04-08 45.6 MB
doltgresql-darwin-arm64.tar.gz 2026-04-08 45.0 MB
doltgresql-darwin-amd64.tar.gz 2026-04-08 47.7 MB
doltgresql-linux-arm64.tar.gz 2026-04-08 44.6 MB
doltgresql-linux-amd64.tar.gz 2026-04-08 48.3 MB
0.56.1 source code.tar.gz 2026-04-08 12.0 MB
0.56.1 source code.zip 2026-04-08 13.6 MB
README.md 2026-04-08 3.1 kB
Totals: 10 Items   283.5 MB 0

Merged PRs

doltgresql

  • 2560: Fixed issues 2547 and 2557 This fixes:
  • https://github.com/dolthub/doltgresql/issues/2547
  • https://github.com/dolthub/doltgresql/issues/2557 This introduces a new function type which mirrors the C-language variadic function implementation. These functions differ from standard PostgreSQL variadic functions, as normally variadic functions require that all variadic parameters have the same type. This limitation is not true for C-language functions. This was required to implement a valid concat function, as we were previously relying on GMS' built-in version, which is not correct for Postgres. I also corrected some tests that enforced the incorrect behavior. This also fixes a bug in JSON parsing. It was already known that Go's JSON library converts escaped characters into their original forms, however we were attempting to preemptively handle the incorrect conversion. This has been changed, as we can cleanup the output since the unescaped forms are invalid JSON anyway, which fixes the behavior and makes our output more accurate.
  • 2554: Fixed issues 2546 and 2548 This PR fixes:
  • https://github.com/dolthub/doltgresql/issues/2546
  • https://github.com/dolthub/doltgresql/issues/2548
  • 2529: Fixed ANY using bindings This fixes:
  • https://github.com/dolthub/doltgresql/issues/2386 In GMS/MySQL, we often can't determine the type of a bound parameter during the initial parse as the return type is subject to the input (binding a float32 vs int32 may result in an actual return type difference). This is not true for Postgres as type resolution is very well defined. This creates a mismatch where we defer the type resolution, but the client expects to be told what type the bindings should be. We should have a more general solution that covers bindings at the GMS layer for how MySQL and Postgres handle type resolution differently, but the scope of that project seemed too large for now, so this only implements a local fix specifically for the issue linked above.
  • 2501: allow running multiple statements in function

Closed Issues

  • 2546: SELECT 'foo' --> invalid OID 705
  • 2547: concat('', NULL, '') incorrectly returning null string
  • 2548: Timezone parser does not accept PostgreSQL-accepted formats (time zone offset)
  • 2545: Suggestion: include Doltgres brand in version string
  • 2557: unescaped newlines in JSON output
  • 2423: information_schema.columns cannot be queried with dolt_show_system_tables set
  • 2386: Error when running parameterized any clause.
Source: README.md, updated 2026-04-08