Long ago we set a pg_temp in "Extra search path" to debug with Supabase team our issue with bloated pg_temp schema. We never removed it and when we updated our instance who upgrade PostgREST to v13 this became a problem and crashed PostgREST in loop. This Change was made years ago and forgotten. We are sorry for this, and will be more careful to revert our test in prod when we have issue.

The issue is resolved, it seems a config got modified in supabse without us chaging it, we are looking in supabase to find a solution to never have this again

Supabase seems to have fix the issue ! We are waiting final update from them

Supabase upgraded plan got effective we got quick answer they are looking into it finally

We got answer in Supabase Discord but it just said wait for support to answer...

We upgraded Supabase plan to enterprise support level to try to get faster response.

We tried to reboot our Supabase infrastructure, enable disable API, nothing works it seems our only solution is to wait Support to answer

We tried to rotate ourself the JWT with what we have avaiable in Supabase UI and nothing works. We opened a ticket in they support, tagged them on X and DM the CEO.

We identified the issue. It's due to the change Supabase is rolling for their JWT auth system. We currently dont have any control on that and reached them to find a solution. You user can still receive updates, certain feature from CLI still works

After doing maintenance on our Database, update to a minor version. Login started to fail in the webapp. Updates are working as expected