Creating a separate database or using a new schema in postgres db

[AliAfsharii]

I prefer to have separate databases for my projects alongside the default "postgres" db but it prevents me from having some dashboard features which are porvided only for postgres db. so I have some questions in that regard.

1. Is there any way to activate dashboard features like logs and advisors for other databases that default "postgres"?
2. If question 1 is not possible, by using a separate db, will I miss any other features than logs and advisors?
3. Will normal db backups include other dbs and restore them as well?
4. Will point in time backup work with other dbs than "postgres"?

and in general please provide your opinion about having separate database for my projct in comparison with using a separate schema in postgres database.

[silentworks]

1. No
2. You will miss all the dashboard features, it will just be a postgres database that you can access with whichever postgres tool. Also this isn't recommended as now your databases are sharing resources.
3. I highly doubt this. I'm not a Supabase staff so take this one with a pinch of salt.
4. Same as point 3

You are given two free projects with your account so you can have two different projects. If you are on paid plan you pay $10 for additional projects so you can have a complete separate db with everything you need.

[AliAfsharii]

@silentworks thanks for your response.
In fact so far I don't use any database feature provided by dashboard except backup, I just create a db and use it directly in my backend.
I have one paid account and tested daily backups and seems it restore all dbs, not only the default postgres but for point of time I am not sure.
I prefere to have a separate db to be alway sure that we know what is happening in it and what extensions are installed there.
I may be overthinking it too much.