garyaustin

Old https://pganalyze.com/blog/5mins-postgres-jsonb-toast but I see multiple references to anything above 2k requiring special handling and the bigger the slower as it all has to be processed...

I agree. You should make a feature request to Supabase.

Well... rpc to do SQL is the only way to do a partial update. But a 10MB json object is pretty big for Postgres. You should research postgres and json/b columns and size and performance. Well beyond anything I've seen.

On 2nd question ... no idea what nodes are and what trace you are referring to. Check the supabase logs to see if there is more info or query performance if you have a query timing out.

The REST API is all json in the column for updates. You could use an rpc call and SQL to target exactly what you want.

So you do have 2fa enabled in Supabase it looks like ... correct? If so then you will likely need to contact support@supabase.com if the code is what is being sent. Not much users here can do. You are also posting on a pretty old thread and likely won't get other users to see this... but not sure they can help.

https://supabase.com/docs/guides/integrations/vercel-marketplace#studio-support This implies at least one method you get to the dashboard thru Vercel.

Are you sure there is a supabase account if you signed up thru v0? Did you ever use the supabase dashboard as part of the process?

Still had my test function/trigger running.

It is still doing 2...

Just add a trigger function for all ops and raise log with the OP and NEW to see what is going on.

https://github.com/supabase/storage/blob/master/src/storage/uploader.ts#L49 This MIGHT be the code. Just a quick look, but their code is pretty spread out.

It is very dangerous to rely on triggers on their operations.

As I warned in that it can change at anytime and I have no idea what supabase does in the code now (it took awhile to find it back then). Did you add a trigger and raise log to see what the inserts were? The first one was used to test RLS and would error back and I know they rolled that transaction back so the row was removed in the code at that time. I also know the 2nd insert was AFTER the s3 write because it has metadata from s3. But I don't remember looking at the code to see what happens if the 2nd insert failed.

No idea. You should start a new topic though and not add on to something not in the title. Neither of us are Kotlin users IF it is related to that. Check your auth logs and details to determine what exactly is getting the timeout and maybe a reason. Are other operations failing? Can you signup a user from the authentication panel? Is your project status good?

Nothing built in for either idtoken or oauth to send additional data.

Check your usage as I added above. Have you tried a restart?

<@111560214536314880> Is this for the dashboard or app? What is the status showing on the home page of the project? No other reports here of any outages. Any usage issues (check usage in settings and database report in observability).

I don't find a limit in supabase/auth in a quick search (low confidence). But I do find this in the dashboard UI code: https://github.com/supabase/supabase/blob/2ae4942cbb41050051f8e4ee6cc80b5e944d0904/apps/studio/components/interfaces/Auth/RedirectUrls/RedirectUrls.tsx#L54 See image. Max is 2*1024.

It happens and only support can solve it.

This is a user helping user forum mainly, so you are waiting on a user who has a setup like this to see your post. If you can't test it yourself then support might be able to tell you.

https://discord.com/channels/839993398554656828/1006358244786196510

It will gradually restore burst I/O over a 24 hour period is what we found looking at aws documentation for the feature (it is credits "earned" over time up until a max).

Never seen that commented on. Free plans get 7 days of backups if turned to Pro, but whether Supabase stores more than that routinely would be something you would have to ask them about. I'm skeptical.

Otherwise support@supabase.com

Did you try another device/vpn/browser? Check your past emails to make sure the right account? Did you signup with Github and are trying to login with email?

Yes, you have to contact support.

This is mainly a user helping user forum, but no. Not seen any discount Pro plans.

We have an informal queue to bump projects in general support but normally pro support is faster than that. ..... If you got that email then nothing can be escalated from here as we only have the above ability thru one employee. Infra team will work on projects in the order they are received. This forum is not monitored by staff regularly, and no employee can bump things like this in the infra queue anyway as all in the queue are in the same situation.

Did you get the email it was moved to the infra team already?

Pro plans can't be paused. Did you upgrade after pausing? Why did you get paused? If your ticket was forward to infra team nothing we can do for you here.

But sounds like you have support moving on it, which is the way to go.

I'm a user.

Posting here does nothing really as this is a user helping user site mainly.

You are Team and support has not got back with you?

Free can be a day or more. We have an informal path to bump these kind of tickets that ONE employee checks when he can. I'll add it to that.

Free or Pro?

How long?

It was created to allow linking different emails from different auth providers versus the default linking for the same email. https://supabase.com/docs/guides/auth/auth-identity-linking#manual-linking-beta

You should start a support request. There is nothing you can do from your side to solve it if it does not resolve itself.

This is the API methods for linking... https://supabase.com/docs/guides/auth/auth-identity-linking

How do you do that if it is already being used in an auth.users row? You would have to remove the old row first. And you have to deal with all other auth tables (like identitiies) that link to it. If they have existing data in an original account seems like adding their new login identity to that is easier than trying to delete all uses of an id and then replaces all uses for another.

That UUID is used in many auth tables and possibly your data tables depending on what they have done.

Are you sure you can't just use the account they want to go to and link the new login info to it?

You also have to modify all references to the other id.

You could but it can't be the same as another UUID.

You can link a signup to the account so both accounts are the same user_id. You can't have two accounts with the same id.

There is only identity linking built in. It is usually done when signing up though. There is nothing built in to merge existing user accounts especially if data tables use the uuid to both.

No one reporting anything in particular that I've seen. What operation is timing out? What is the status of your project?

Check the status of your project on its home page.