mirror of
https://github.com/neondatabase/neon.git
synced 2025-12-24 22:59:59 +00:00
## Problem We currently don't run end-to-end tests for PostgreSQL extensions on our cloud infrastructure, which means we might miss problems that only occur in a real cloud environment. ## Summary of changes - Added a workflow to run extension tests against a cloud staging instance - Set up proper project configuration for extension testing - Implemented test execution with appropriate environment settings - Added error handling and reporting for test failures --------- Co-authored-by: Alexander Bayandin <alexander@neon.tech> Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
8 lines
491 B
Bash
Executable File
8 lines
491 B
Bash
Executable File
#!/bin/sh
|
|
set -ex
|
|
cd "$(dirname ${0})"
|
|
dropdb --if-exist contrib_regression
|
|
createdb contrib_regression
|
|
psql -d contrib_regression -c "CREATE EXTENSION vector"
|
|
PG_REGRESS=$(dirname "$(pg_config --pgxs)")/../test/regress/pg_regress
|
|
${PG_REGRESS} --inputdir=./ --bindir='/usr/local/pgsql/bin' --inputdir=test --use-existing --dbname=contrib_regression bit btree cast copy halfvec hnsw_bit hnsw_halfvec hnsw_sparsevec hnsw_vector ivfflat_bit ivfflat_halfvec ivfflat_vector sparsevec vector_type |