Last versions of PostgREST doesn't work if the SCHEMA name contains uppercase characters

[Pigeo]

Environment

• PostgreSQL version: 12 or 15 (tested on both)
• PostgREST version: 13.0.8 or 14.16 (tested on both)
• Operating system: Debian 10 or 11 (tested on both)

Description of issue

I have a working setup in production (since several years) with an old version of PostgREST.
Trying to upgrade it to PostgREST 13 or 14, I've got the following error on any HTTP requests:

{
  "code": "3F000",
  "details": null,
  "hint": null,
  "message": "schema \"rest_api_v1_0\" does not exist"
}

My PostgREST config file contains:

db-schema = "REST_API_v1_0"

It seems that SCHEMA names containing upper cases character are no longer working with PostgREST 13 ou 14 (it was working correctly with all the previous versions I used, at least from to PostgREST 7 to 12)

[Pigeo]

May I remind you what I suggested about unit tests in #2341 (comment)

If this suggestion had been done... This new bug would have been immediately triggered during unit tests...

Thanks in advance

[steve-chavez]

Not reproducible, I've tried v14 and v16:

---
 test/spec/fixtures/schema.sql | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/test/spec/fixtures/schema.sql b/test/spec/fixtures/schema.sql
index cce6136e..6dba64c3 100644
--- a/test/spec/fixtures/schema.sql
+++ b/test/spec/fixtures/schema.sql
@@ -3892,3 +3892,11 @@ create function never_uses_prepared_statements() returns bool as $$
   select count(*) = 0 from pg_catalog.pg_prepared_statements
   where statement ilike '%never_prepared%';
 $$ language sql;
+
+create schema "REST_API_v1_0";
+
+grant usage on schema "REST_API_v1_0" to postgrest_test_anonymous;
+
+create table "REST_API_v1_0".projects (id int, name text);
+
+grant all on "REST_API_v1_0".projects to postgrest_test_anonymous;
-- 
2.40.1

PGRST_DB_SCHEMAS="REST_API_v1_0" PGRST_LOG_QUERY=true PGRST_DB_POOL=10 PGRST_DB_PLAN_ENABLED=true PGRST_LOG_LEVEL=debug postgrest-with-pg-17 -f test/spec/fixtures/load.sql postgrest-run

$ curl 'localhost:3000/projects'
[]

Logs show the correct query produced:

10/Aug/2026:20:38:04 -0500: select set_config('search_path', $1, true), set_config('role', $2, true), set_config('request.jwt.claims', $3, true), set_config('request.method', $4, true), set_co
nfig('request.path', $5, true), set_config('request.headers', $6, true), set_config('request.cookies', $7, true)
10/Aug/2026:20:38:04 -0500: WITH pgrst_source AS ( SELECT "REST_API_v1_0"."projects".* FROM "REST_API_v1_0"."projects"    )  SELECT null::bigint AS total_result_set, pg_catalog.count(_postgres
t_t) AS page_total, coalesce(json_agg(_postgrest_t), '[]') AS body, nullif(current_setting('response.headers', true), '') AS response_headers, nullif(current_setting('response.status', true), 
'') AS response_status, '' AS response_inserted FROM ( SELECT * FROM pgrst_source ) _postgrest_t
127.0.0.1 - postgrest_test_anonymous [10/Aug/2026:20:38:04 -0500] "GET /projects HTTP/1.1" 200 2 "" "curl/7.81.0"

[steve-chavez]

Could be related, on v13 we started validating the schema names b6863f1. Prior to v13 we were lenient and let you start with invalid schemas on db-schemas. Now if you start with an invalid schema you'll get failures at startup.

"message": "schema "rest_api_v1_0" does not exist"
db-schema = "REST_API_v1_0"

What's the actual schema name on the database?

[Pigeo]

pageorge@thesoc ~$ sudo -u postgres psql -d THESOC
psql (15.18 (Debian 15.18-1.pgdg11+1), server 12.22 (Debian 12.22-4.pgdg11+1))
Type "help" for help.

THESOC=# \dn
          List of schemas
     Name      |       Owner       
---------------+-------------------
 GEO_IP        | THESOC
 REST_API_v1_0 | api_views_creator
 THESOC        | THESOC
 public        | postgres
 rest_api_v2_0 | postgres
(5 rows)

THESOC=# 

I'm sorry but the actual schema name on the database is "REST_API_v1_0" 😬

I also confirm you that on my side, it's not working on PostgREST 14.16 with PostgreSQL 15

Any ideas?

[steve-chavez]

@Pigeo Please post your full configuration file (redacted URI) plus the contents of pg_db_role_setting (in case the in-db config is overriding db-schemas).

[wolfgangwalther]

Any ideas?

Looking at the output you posted, I see that the two version of rest api schemas have a different owner. Are you sure this is not a permission problem somehow?