self-host storage got relation "buckets" does not exist thought schema and tables already exists about storage HOT 9 CLOSED

Hello @glani the image is now available 0.44.1
Also not sure i understand what you by is not checked for creation?

If you want to disable role creation you would want to pass the DB_INSTALL_ROLES=false as an env.
This is useful if the roles are created externally from storage

from storage.

Hello @customkandura could you please provide the records of your migrations table under the storage schema?

from storage.

Interestingly a new connection url to cloud hosted storage DB causes the same error. Looks like a balancer always points to public scheme instead of "storage".
Steps to reproduce are simple.
I created a project:
Spawned a storage service in docker (I need it because the configuration of cloud version is pretty weak)
connection via pgbouncer works smoothly. However when I switched to AWS balancer of postgres all queries started failing with the above mentioned issue.

on the 15th of January there will be no support anymore for pgbouncer and looks like the current solution is pretty raw.

from storage.

@customkandura I have dug deeper into this issue and apparently the original error was caused by not having the initial migration as part of the service.

My recent PR #409 will now include the initial migration and the Storage service will now start without manually run the migrate command.

A release is yet to be done for this feature I'll keep you up to date.

@glani Storage requires the pooler to support either transaction mode or session where transaction mode is the preferred setting for optimum performance.

Could you please link the AWS pool service you are trying to use, i'll have a look at their docs. Also can you make sure the DATABASE_POOL_URL env is set with the correct user

from storage.

@fenos now it starts working when I specified DATABASE_POOL_URL. When a new docker image will be available or release ? I built a current master to check it. However, merged PR of a new migration system is very questionable (b0331a1). No way to deploy it as independent database with storage schema. Role "authenticator" is not checked for a creation.

from storage.

Closing the issue as this is now supported

from storage.

here is a docker-compose file example:
https://github.com/supabase/storage/blob/master/docker-compose.yml

from storage.

Hello @glani the image is now available 0.44.1 Also not sure i understand what you by is not checked for creation?

If you want to disable role creation you would want to pass the DB_INSTALL_ROLES=false as an env. This is useful if the roles are created externally from storage

this solved also my issue with supabase/storage-api:v0.46.3 ! thanks a lot! had the problem that storage migrations failed with role "anon" already exists

from storage.

from storage.