PostgREST schema cache not updating - PGRST204 errors

# Bug report - [x] I confirm this is a bug with Supabase, not with my own application. - [x] I confirm I have searched the [Docs](https://docs.supabase.com), GitHub [Discussions](https://github.com/supabase/supabase/discussions), and [Discord](https://discord.supabase.com). ## Describe the bug PostgREST schema cache does not update when new columns are added to existing tables or when new tables are created. The cache persists stale information despite all documented refresh methods. This makes it impossible to extend the database schema in production. **Error Code:** `PGRST204` **Error Message:** `"Could not find the 'column_name' column of 'table_name' in the schema cache"` ## To Reproduce Steps to reproduce the behavior: 1. **Add a new column to existing table:** ```sql ALTER TABLE planting_plans ADD COLUMN batch_number TEXT; ``` 2. **Verify column exists in database:** ```sql SELECT column_name FROM information_schema.columns WHERE table_name='planting_plans' AND column_name='batch_number'; -- Returns: batch_number ✓ ``` 3. **Attempt to use new column via PostgREST API:** ```javascript const { data, error } = await supabase .from('planting_plans') .insert({ batch_number: 'TEST-123', /* other fields */ }); ``` 4. **See error:** ```json { "code": "PGRST204", "message": "Could not find the 'batch_number' column of 'planting_plans' in the schema cache" } ``` **Attempted cache refresh methods (NONE worked):** ```sql -- Method 1 NOTIFY pgrst, 'reload schema'; -- Method 2 NOTIFY pgrst, 'reload config'; SELECT pg_reload_conf(); -- Method 3 GRANT ALL ON TABLE planting_plans TO anon, authenticated, service_role; NOTIFY pgrst, 'reload schema'; -- Method 4: DROP and recreate ALTER TABLE planting_plans DROP COLUMN batch_number; ALTER TABLE planting_plans ADD COLUMN batch_number TEXT; GRANT ALL ON TABLE planting_plans TO anon, authenticated, service_role; NOTIFY pgrst, 'reload schema'; -- Method 5: Project restart via Dashboard -- Paused project → Resumed → Still…