doltgres 0.52.0

[BrewTestBot]

Created by brew bump

---

Created with brew bump-formula-pr.

release notes

# Merged PRs
doltgresql

1858: Added SQL scrubber and scrubbed SQL file

This adds a scrubber program that can take a SQL file and scrub all information from it, replacing it with random data (while still following referential data). Additionally, this adds a scrubbed SQL file, and creates a new GitHub action since these tests can take a bit longer (since SQL files can be megabytes in size).
1848: Fixed numerous import issues

This fixes numerous issues as seen from importing customer dumps. I'm currently scrubbing the dump of all sensitive or identifying information of any kind, which I'll include in a follow-up PR, alongside the tool built to allow us to scrub any future dumps so that we may keep them within our test suite. As a result, I didn't include any direct tests in this PR since the dump will fulfill the requirements.

Requires:

Reverted Extended encoding from adaptive to ref dolthub/dolt#9832


1833: Fixed INDEX reservation

Some dumps include columns that are named "index", which is forbidden in CockroachDB. Our parser was initially based on an open-licensed version of CockroachDB's parser (Postgres Parser Added dolthub/doltgresql#19 (comment)), and we therefore inherited some of the restrictions that CockroachDB has. We want our customers to be able to use standard Postgres dumps, so this removes the CockroachDB extensions and restores the functionality expected of Postgres users. We didn't implement functionality for the extensions anyway, so this should be a harmless removal.

For reference, this is the page discussing the extensions:

https://www.cockroachlabs.com/docs/stable/order-by
1830: Zachmu/pg indexes
1826: support datestyle parameter use

Depends on allow setting session variable default value dolthub/go-mysql-server#3203
1818: .github/workflows: Add ICU4C to places where we build and test doltgresql.
1811: add make_timestamptz functions
1809: Added SQL import testing framework

One thing that we'll be adding is tests to ensure that imports from all over not only work in Doltgres, but continue to work. To achieve this, this PR adds a new framework that allows us to specify files that will be imported, as well as allowing for any needed setup that an import may need (such as user creation). Additionally, as import files may be very, very large, we needed a good way to attach errors to their origin queries. This framework gives an experience that is as close to standard Go debugging as we can get, considering imports must be done through PSQL (or pg_restore, which isn't supported yet, but would function very similarly to the PSQL path).

To reiterate, this gives us:

Focus capability on specific dumps
Error reporting for associating errors with queries
Breakpoint triggers for specific queries
Repeatable testing to ensure import compatibility doesn't regress


1806: In-memory indexes for pg_class

See Refactorings to support index scans for pg catalog tables dolthub/go-mysql-server#3190

This is a proof of concept for pg_class. Other pg_catalog tables are next.
1795: /servercfg/config.go: update config to have mcp methods
1793: .github: New releases are no longer prerelease
1792: ALTER TABLE changes for migration scripts

This adds support for some sequence-related statements from a customer-provided dump for the purposes of testing imports.
1757: add more date and time functions

Closed Issues

1056: dolt_history_$tablename sometimes returns wrong rows for tables with same name in different schemas

View the full release notes at https://github.com/dolthub/doltgresql/releases/tag/v0.52.0.

---

[chenrui333]

  # github.com/dolthub/go-icu-regex/internal/icu
  /home/linuxbrew/.cache/Homebrew/go_mod_cache/pkg/mod/github.com/dolthub/[email protected]/internal/icu/icu.go:8:11: fatal error: unicode/uregex.h: No such file or directory
      8 | // #include "unicode/uregex.h"
        |           ^~~~~~~~~~~~~~~~~~
  compilation terminated.

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Caution

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.