Validate production with PgBouncer can read/write table in new schema
In &6451 (closed), we propose to use database schemas. Particularly we will :
- create new
gitlab_ci
schema. - Move CI related tables to
gitlab_ci
schema. - Not set
production.schema_search_path
inconfig/database.yml
This issue is about validating that we can set up search path for the pgBouncer role / connection and we can access a table that has been moved to the gitlab_ci
schema.
We have two options:
- Find a low/non-impactful table to move to
gitlab_ci
schema. - Make a test table/model and use that new model in a test page.
Why ?
- Consistency of development to production
- No need to constantly switch between schema, and schema-less
Why not ?
- We still have not solved how self-managed will migrate to DB schemas
Edited by Thong Kuah