alter table gives me a successful response when it should fail on not existing schema

[aizerin]

I have a problem with my database when I try to alter any table. I think it it because I got success response to every SQL command, even when it does not make sense.

For example when I run this alter table nott.exists set schema foo. I will get Success. No rows returned. But it should give me ERROR: 3F000: schema "nott" does not exist

I used Prisma to migrate, but switched to the Supabase solution. I think Prisma broke something in the database, but I don't know exactly what.

When I create a preview branch and apply the migration files, everything works as expected. I tried to dump the DB and diff it with the production DB, but I didn't find anything useful.

[GaryAustin1]

This appears to be a bug on older instances for some period. Upgrade your Postgres in infrastructure.

[aizerin]

Thank you, that solves the problem. I will check updates more often in future.