_k1ngarthur

definitely write to support i think

those queries do not seem that slow to me

what is the time of those queries?

do you have any queries taking a very long time?

https://supabase.com/dashboard/project/_/observability/query-performance?sort=prop_total_time&order=desc

i think a custom access token is the only way to test this and my suspicion is that supabase does not enforce aud='authenticated' if it allows you to change it but you can modify RLS policies to do that check if you want. I would just test and see what happens, i couldn't find anything more official than what i shared so you would have to reach out to supabase support for official answers

could you spin up a test project with a custom access hook where you modify the JWT https://supabase.com/docs/guides/auth/auth-hooks/custom-access-token-hook?queryGroups=language&language=sql audience?

what is it that you want to test? if the aud does not equal authenticated you want it rejected?

https://supabase.com/dashboard/project/_/observability/database starting from here would be good

also ask/check if any of the usages look very high

What i am thinking is that this is some issue with the project/instance that support has to fix but you have to determine if anything in the logs points to an actual error

i would ask the AI are there any errors in the log that point to some issue in supabase resolvable by myself.

sounds good

no there shouldn't be but if the auth server is the issue which it seems like it is from above then restarting the project might help fix the underlying issue. That is the only thing that comes to mind as a potential solution for now

did you restart just your database or your entire project/instance?

any messages that explain the nature of the error?

check the api gateway logs for the error requests and see what it returns

ahh you are not connecting directly to the database so what do you mean losing the connection then? You try and make a request and it just fails?

How are you connecting to your database? What type of connection string are you using?

try a VPN but this might be related to <#1409892722474614814>

This is a user helping user forum and not official supabase support. Does anyone else have acces to this project to transfer your ownership from it?

what error are you seeing when you try and login

do you happen to have a developer account or are you admin/owner of this project?

why are you so sure that it was linked to the old native account? if it is because of a missing project there are other potential causes

i don't even believe it is possible to have two supabase accounts with the same email. All sign in attempts with github should lead to the one and only email account

https://supabase.com/docs/guides/platform/manage-your-usage/logs-query here is a doc about optimising logs from supabase

what i am saying is you want to optimise these numbers because you think they are high but because those high numbers are caused by a bug you won't know if what you did made a change or even if it is required

see https://discord.com/channels/839993398554656828/867290243216310272/1562428242961629257

yeah i can't think of an alternative besides scraping the metrics API unfortunately

Query logs aren't charged until the new year anyway

This look like a bug at the moment https://discord.com/channels/839993398554656828/1561684422237884456/1561883407208677439

yeah that is another option as well, if you don't have any migrations in supabase_migrations.schema_migrations then branches will automatically copy over from prod but those issues you found are what i was worried about that the diff can sometimes cause. The thing is you ideally want to have a history of migrations i assume hence why i suggested baselining the schema

Did anything happen before running this catalog investigation? Like an restart or something else?

It does seem like catalog corruption but it won't help you know which relation is the active one as since pg_class is restricted only support can make changes to resolve this so waiting for them to diagnose/help seems like the only call.

some of us on support already get paid by supabase for helping out on the server and other places so seems like a bit of a conflict of interest to take additional paid work, i'm happy to continue on the thread if you have more questions (but it would be intermittent throughout the day). If you are looking for more dedicated help then <#1109966433431080960> is probably the way to go

no worries

this is a user helping user server so support won't see this message. I should mention that support can take a while to get back to you if you are free so if it really is urgent then i suggest upgrading at lease for a month then downgrading again later

you have to reach out to support to see if they will be willing to give relief

Hi there, you marked this as solved. Did you get an answer?

just th emigration history of prod is now being put into a new file but i have seen some people have issues before where they needed to modify manually the migration because the way it diffed it for declarative schemas wasn't entirely accurate

this won't affect prod in anyway

yeah this is what i would do

what does this trigger do?

there is no way to alter tables inside of protected schemas usually

hmm okay, i would make sure you have a local copy of all of your current migrations before doing what i said above in case what i suggested is not the issue

i would see what support says but also if you could report back that might help for other users also

i have seen a few other posts where people have high log query https://discord.com/channels/839993398554656828/1560414529240965202

so is it that it only got 25 migrations through before failing?

so the next time you open a branch it would use that schema which should be a copy of production and then obviously going forward make sure all other changes are mapped in a migration

and then https://supabase.com/docs/reference/cli/supabase-db-pull hould create a new schema which is a replica of your current production database