mirror of
https://github.com/neondatabase/neon.git
synced 2025-12-22 21:59:59 +00:00
## Problem The information in the README.md contained errors, and some information was missing. ## Summary of changes Found errors are fixed, and new information is added. --------- Co-authored-by: Alexander Bayandin <alexander@neon.tech>
How to run the pg_regress tests on a cloud Neon instance.
- Create a Neon project on staging.
- Grant the superuser privileges to the DB user.
- (Optional) create a branch for testing
- Add the following settings to the
pg_settingssection of the default endpoint configuration for the project using the admin interface:Timeone:America/Los_AngelesDateStyle:Postgres,MDYcompute_query_id:off
- Add the following section to the project configuration:
"preload_libraries": {
"use_defaults": false,
"enabled_libraries": []
}
- Checkout the actual
Neonsources - Patch the sql and expected files for the specific PostgreSQL version, e.g. for v17:
$ cd vendor/postgres-v17
$ patch -p1 <../../compute/patches/cloud_regress_pg17.patch
- Set the environment variables (please modify according your configuration):
$ export DEFAULT_PG_VERSION=17
$ export BUILD_TYPE=release
- Build the Neon binaries see README.md
- Set the environment variable
BENCHMARK_CONNSTRto the connection URI of your project. - Update poetry, run
$ scripts/pysync
- Run
$ scripts/pytest -m remote_cluster -k cloud_regress