Project-specific PostgREST schema cache stuck – PGRST002 errors
Here’s a fully Markdown-formatted version you can copy-paste directly:
json
{
"response": {
"error": {
"code": "PGRST002",
"details": null,
"hint": null,
"message": "Could not query the database for the schema cache. Retrying."
},
"data": null,
"count": null,
"status": 503,
"statusText": "Service Unavailable"
}
}
sql
select * from packages_schema.general;
ts
const supabase = createClient(
process.env.SUPABASE_URL!,
process.env.SUPABASE_ANON!,
{ db: { schema: "packages_schema" } }
);
const { data, error } = await supabase.from("general").select("*");
This is concise, readable, and ready to paste into Supabase support.
```
json
{
"response": {
"error": {
"code": "PGRST002",
"details": null,
"hint": null,
"message": "Could not query the database for the schema cache. Retrying."
},
"data": null,
"count": null,
"status": 503,
"statusText": "Service Unavailable"
}
}
sql
select * from packages_schema.general;
ts
const supabase = createClient(
process.env.SUPABASE_URL!,
process.env.SUPABASE_ANON!,
{ db: { schema: "packages_schema" } }
);
const { data, error } = await supabase.from("general").select("*");
This is concise, readable, and ready to paste into Supabase support.
```
