element-hq / element-hq/synapse
running synapse_port_db on an existing database will bork it
Open
A-Portdb
S-Minor
T-Defect
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 600
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 51
Description
This issue has been migrated from [#5739](https://github.com/matrix-org/synapse/issues/5739).
---
It seems like a silly thing to do, but people might run synapse_port_db on an existing postgres database either by mistake or because a misguided [ansible playbook](https://github.com/Madic-/matrix-synapse-auto-deploy/blob/master/tasks/postgres.yml) does it for them. This will end up with a rather broken database, including at least [missing `profile` entries](https://github.com/vector-im/riot-web/issues/10175).
Can we add some safety guard that will stop you running port_db on a database which has already been ported?
Contributor guide
Assessment
This issue has not been assessed yet.