Slavi Pantaleev dd797ba6a7 Fix Postgres database importing/upgrading conflicts ... We were running into conflicts, because having initialized the roles (users) and databases, trying to import leads to errors (role XXX already exists, etc.). We were previously ignoring the Synapse database (`homeserver`) when upgrading/importing, because that one gets created by default whenever the container starts. For our additional databases, it's a similar situation now. It's not created by default as soon as Postgres starts with an empty database, but rather we create it as part of running the playbook. So we either need to skip those role/database creation statements while upgrading/importing, or to avoid creating the additional database and rely on the import for that. I've gone for the former, because it's already similar to what we were doing and it's simpler (it lets `setup_postgres.yml` be the same in all scenarios).		2020-12-14 22:28:20 +02:00
..
defaults	Fix Postgres database importing/upgrading conflicts	2020-12-14 22:28:20 +02:00
tasks	Fix Postgres database importing/upgrading conflicts	2020-12-14 22:28:20 +02:00
templates	Don't mention Postgres roles, just say users	2020-12-14 10:04:37 +02:00