PostgREST Only Exposing First Schema in PGRST_DB_SCHEMAS List

[gabrielstellini]

Environment

• PostgreSQL version: postgres:15
• PostgREST version: v12.0.1
• Operating system: Linux, Debian

Description of issue

The following is a sample from my docker-compose file:

  postgrest:
    container_name: postgrest
    image: postgrest/postgrest:latest
    ports:
      - 8082:3000
    environment:
      - PGRST_DB_URI=postgres://${APP_DB_USER}:${APP_DB_PASSWORD}@postgres:5432/${APP_DB}
      - PGRST_DB_ANON_ROLE=pg_custom_anon
      - PGRST_DB_SCHEMAS=schema1,schema2,schema3
      - PGRST_JWT_ROLE_CLAIM_KEY=[CENSORED]
      - PGRST_JWT_SECRET=${PGRST_JWT_SECRET}
      - PGRST_JWT_SECRET_IS_BASE64=false

Expected Behavior:
When I specify multiple schemas in the PGRST_DB_SCHEMAS environment variable, I expect all listed schemas to be loaded and exposed via the API. The docs specify that this parameter should accept a list

Actual Behavior:
Only the first schema listed in PGRST_DB_SCHEMAS is being exposed by the API. Reordering the schemas results in only the first schema being exposed. The exposed tables are reflected in swagger, and reordering effects the swagger definition to reflect this

[laurenceisla]

The API only accesses one schema at a time. By default it's the first one in the list. For example, in order to get a table from schema2, you need to specify it in the Accept-Profile header, e.g.:

curl "http://localhost:3000/table" -H "Accept-Profile: schema2"

See the Schema section in the docs for more info.

The OpenAPI output also needs to be accessed using the "Accept-Profile" header, otherwise it will show info for the first schema by default. Nginx can help you in defining different locations for each schema (by adding that header to their respective location).