supabase_storage_admin clarification

My database is being bombarded by connections from usename

supabase_storage_admin

supabase_storage_admin

supabase_storage_admin

supabase_storage_admin having hard time figuring out why and what it is that it does. Can anyone help?

garyaustin•9/29/25, 4:25 PM

Where are you seeing these connections?
Logs with accesses? Roles with active connection amount large?

Would see that is Supabase storage server calling your DB for info but not sure as I only see one connection and don't know of it showing up in a log.

garyaustin•9/29/25, 5:12 PM

Can you check the status of your instance on the home page for the project?

KapxyOP•9/29/25, 5:27 PM

I checked with

-- View all connections
 SELECT
   pg_stat_activity.pid,
   ssl AS ssl_connection,
   datname AS database,
   usename AS connected_role,
   application_name,
   client_addr,
   query,
   query_start,
   state,
   backend_start
   
FROM pg_stat_ssl
JOIN pg_stat_activity
 ON pg_stat_ssl.pid = pg_stat_activity.pid
where usename = 'supabase_storage_admin'

-- View all connections
 SELECT
   pg_stat_activity.pid,
   ssl AS ssl_connection,
   datname AS database,
   usename AS connected_role,
   application_name,
   client_addr,
   query,
   query_start,
   state,
   backend_start
   
FROM pg_stat_ssl
JOIN pg_stat_activity
 ON pg_stat_ssl.pid = pg_stat_activity.pid
where usename = 'supabase_storage_admin'

Theres 43 right now, earlier I saw 65

garyaustin•9/29/25, 5:27 PM

Is this a brand new instance?

KapxyOP•9/29/25, 5:27 PM

No, quite old and in production use

garyaustin•9/29/25, 5:31 PM

I'd file a support request then.

KapxyOP•9/29/25, 5:32 PM

All queries are just COMMIT; or ROLLBACK; as well so that doesnt help finding out what they are

garyaustin•9/29/25, 5:32 PM

Are you doing alot of storage operations?

garyaustin•9/29/25, 5:32 PM

The do use both committ and rollback when uploading files.

KapxyOP•9/29/25, 5:33 PM

Yeah we process quite a lot of images

KapxyOP•9/29/25, 5:33 PM

Do you know why? Can I stop it?

garyaustin•9/29/25, 5:34 PM

Stop what?

KapxyOP•9/29/25, 5:34 PM

The storage calling my database and hogging my connections. Whats the purpose of it?

garyaustin•9/29/25, 5:34 PM

That may be storage doing its thing. I would think though they would be coming in as the role of the user that initiated the request though.

garyaustin•9/29/25, 5:34 PM

It might be creating your files?

garyaustin•9/29/25, 5:35 PM

All uploads go to storage.objects for at least 2 SQL operations.

garyaustin•9/29/25, 5:35 PM

But I'm surprised there would be that many connections.

KapxyOP•9/29/25, 5:36 PM

Well I do have millions of objects. Maybe I should/could do uploads without the sdk as I dont really use the storage schema at all

garyaustin•9/29/25, 5:36 PM

How would you upload?

garyaustin•9/29/25, 5:36 PM

Supabase storage uses the schema storage.objects for everything.

KapxyOP•9/29/25, 5:37 PM

Idk isnt it just S3 in the end?

garyaustin•9/29/25, 5:37 PM

The meta data is all in storage.objects.

garyaustin•9/29/25, 5:38 PM

I know upload does two inserts for each upload one before the s3 operation to test insert RLS and the other after to store the meta info from s3. One is rolled back the other is commited.

garyaustin•9/29/25, 5:39 PM

But I'm surprised it is hogging connections, but I don't know if they use a pooler or not.

KapxyOP•9/29/25, 5:39 PM

Hmm yeah. Feels a bit funny as this is the first time I even notice the storage schema. Apparently I have 8M records for objects

garyaustin•9/29/25, 5:40 PM

I wonder if your insert queries are bogging down...

KapxyOP•9/29/25, 5:40 PM

Can I somehow check if they use pooler? Maybe I could see which port the queries hit?

garyaustin•9/29/25, 5:41 PM

Sorry I don't know that level of detail.

garyaustin•9/29/25, 5:41 PM

Are these uploads for RLS users?

KapxyOP•9/29/25, 5:41 PM

No I do them from a separate backend with service key

garyaustin•9/29/25, 5:42 PM

K. You might look at the query performance report on database to see if the inserts are "dying".
But seems like a support request is in order as that is alot of connections to be eating up.

KapxyOP•9/29/25, 5:43 PM

I'll hit up a support request and lets see what they say.

KapxyOP•10/6/25, 6:45 AM

We have a new local connection pooler feature that I've enabled on your project. This feature makes much more efficient use of connections by re-using connections for multiple concurrent storage requests. This is in addition to pg_bouncer which already sits between the the storage service and your project database to provide project level connection pooling. This change should reduce the impact storage has on your database.

Supabase enabled some Pooler for my Storage. Seems better now.

garyaustin•10/6/25, 1:09 PM

Thank you for reporting back.

SandeshVakale•10/6/25, 5:51 PM

Amazing!!! I sent support request too. Let's see how it goes....
help-and-questionsDatabaseLackOfConnections

-- View all connections SELECT pg_stat_activity.pid, ssl AS ssl_connection, datname AS database, usename AS connected_role, application_name, client_addr, query, query_start, state, backend_start FROM pg_stat_ssl JOIN pg_stat_activity ON pg_stat_ssl.pid = pg_stat_activity.pid where usename = 'supabase_storage_admin'

supabase_storage_admin clarification

Similar Threads

Similar Threads

Similar Threads