PostgREST not recognizing new columns, tables, views or functions

If PostgREST is returning errors by not recognizing new database columns, tables, views or functions, and logging errors similar to:

1
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 PostgreSQL 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:

1
SELECT pg_notification_queue_usage();

This command directly refreshes the PostgreSQL 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.