rust/neon
1
0
Fork 0
mirror of https://github.com/neondatabase/neon.git synced 2025-12-23 06:09:59 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
amasterov/random-ops-add-logical-replication
neon/test_runner/cloud_regress
History
a-masterov 5be94e28c4 Update the documentation of the cloud regress test (#11539) 
## 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>
2025-04-15 11:00:25 +00:00
..
README.md
Update the documentation of the cloud regress test (#11539)
2025-04-15 11:00:25 +00:00
test_cloud_regress.py
ruff: enable TC — flake8-type-checking (#11368)
2025-03-30 18:58:33 +00:00

README.md

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_settings section of the default endpoint configuration for the project using the admin interface:
    • Timeone: America/Los_Angeles
    • DateStyle: Postgres,MDY
    • compute_query_id: off
  • Add the following section to the project configuration:
"preload_libraries": {
    "use_defaults": false,
    "enabled_libraries": []
  }
  • Checkout the actual Neon sources
  • 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_CONNSTR to the connection URI of your project.
  • Update poetry, run
$ scripts/pysync
  • Run
$ scripts/pytest -m remote_cluster -k cloud_regress