Aight, I will try to answer. I have another issue but also connected to the DB, so maybe you find my findings helpful.
TLDR:
So in short, you should not have the same schema for strapi and other applications, though you can easily have multiple schemas and in the same postgres instance
Here is longer version:
-
Strapi does change the whole schema, in fact it fully flushes the db structure but somehow keeps the data itself on any schema changes, like when you change the content-type. I may be wrong because I didn’t check the code directly. So yes it deletes all the alien tables from database. My use case was when wanted to implement my own migrations there, and the extra table to store migrations_versions kept getting removed.
-
No, you shouldn’t ignore it, it will cost you lots of nerves and few new white hairs, if you still have them
-
I believe you misunderstood the statement. It requires all the privileges on that single schema, not all privileges on all schemas.
P.S. I am just another fellow developer using strapi, so I may be wrong