You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a copy of a troubleshooting article on Supabase's docs site. It may be missing some details from the original. View the original article.
If PostgREST is returning errors by not recognizing new database columns, tables, views or functions, and logging errors similar to:
24/Dec/2025:18:16:33 -0500: Failed listening for database notifications on the "pgrst" channel. ERROR: could not access status of transaction 12037872 DETAIL: Could not open file "pg_xact/000B": No such file or directory.
Then this indicates that there's a stale PostgREST schema cache.
Execute the following SQL command via the SQL Editor or a direct client:
select pg_notification_queue_usage();
This command directly refreshes the Postgres notification queue, prompting PostgREST to update its schema cache with the latest database schema. This process is non-disruptive and does not require a database instance or PostgREST service restart.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
This is a copy of a troubleshooting article on Supabase's docs site. It may be missing some details from the original. View the original article.
If PostgREST is returning errors by not recognizing new database columns, tables, views or functions, and logging errors similar to:
24/Dec/2025:18:16:33 -0500: Failed listening for database notifications on the "pgrst" channel. ERROR: could not access status of transaction 12037872 DETAIL: Could not open file "pg_xact/000B": No such file or directory.Then this indicates that there's a stale PostgREST schema cache.
Why this happens
This can occur when an underlying Postgres notification queue issue prevents PostgREST from receiving cache reload signals after schema changes.
How to fix this
Execute the following SQL command via the SQL Editor or a direct client:
select pg_notification_queue_usage();This command directly refreshes the Postgres notification queue, prompting PostgREST to update its schema cache with the latest database schema. This process is non-disruptive and does not require a database instance or PostgREST service restart.
All reactions