rust/neon
1
0
Fork 0
mirror of https://github.com/neondatabase/neon.git synced 2026-01-03 19:42:55 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
eeabecd89f89a24fa8ee642c916efd97b4e8fa06
neon/test_runner/cloud_regress
History
a-masterov 92273b6d5e Enable the pg_regress tests on staging for PG17 (#9978) 
## Problem
Currently, we run the `pg_regress` tests only for PG16
However, PG17 is a part of Neon and should be tested as well 
## Summary of changes
Modified the workflow and added a patch for PG17 enabling the
`pg_regress` tests.
The problem with leftovers was solved by using branches.
2024-12-09 19:30:39 +00:00
..
README.md
Enable the pg_regress tests on staging for PG17 (#9978)
2024-12-09 19:30:39 +00:00
test_cloud_regress.py
Enable the pg_regress tests on staging for PG17 (#9978)
2024-12-09 19:30:39 +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
  • Configure the endpoint by updating the control-plane database with the following settings:
    • Timeone: America/Los_Angeles
    • DateStyle: Postgres,MDY
    • compute_query_id: off
  • 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 variable BENCHMARK_CONNSTR to the connection URI of your project.
  • Set the environment variable PG_VERSION to the version of your project.
  • Run
$ pytest -m remote_cluster -k cloud_regress