-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSC2134 hash lookup database multiple 3pids mapping to a single mxid #29
Comments
On the other hand, in case the same 3pid (assigned to the same mxid) is obtained from more than one backend, the duplicating backend is entirely discarded.
Kind regards, |
Thank you for fixing this. Unfortunately the second part of the issue is still present. Log attached:
Kind regards, |
Just noticed that I am unable to restart ma1sd.
As a workaround I dropped hashes_id_seq. Thank you, |
Triple (mxid, medium, address) should be unique. Could you explain what you means under "backend"? |
Could you please try run ma1sd on the last commit. Or the latest docker image |
Let's say you have both LDAP and SynapseSql identity lookup configured. If a user adds (or already has) the same 3pid in both databases, the mentioned exception occurs. With the last commit I am able to restart ma1sd. Thanks. |
…ibphonenumber-libphonenumber-8.12.42 Bump libphonenumber from 8.12.41 to 8.12.42
Hello,
I noticed a unique key on mxid in table hashes. That way only one 3pid can be assigned to a single mxid.
I have replaced that index with
CREATE UNIQUE INDEX index_hashes_unique_1 ON hashes USING btree (mxid, medium, address);
and it seems fine for the time being.
Kind regards,
Stefan Nikolov
The text was updated successfully, but these errors were encountered: