-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Throws notifcation rotation-related error at 30 second interval #14219
Comments
Odd. Can you connect to the DB and show us what |
Of course! synapse=# \d event_push_summary
Table "public.event_push_summary"
Column | Type | Collation | Nullable | Default
------------------------------+--------+-----------+----------+---------
user_id | text | | not null |
room_id | text | | not null |
notif_count | bigint | | not null |
stream_ordering | bigint | | not null |
unread_count | bigint | | |
last_receipt_stream_ordering | bigint | | |
thread_id | text | | |
Indexes:
"event_push_summary_unique_index" UNIQUE, btree (user_id, room_id)
"event_push_summary_unique_index2" UNIQUE, btree (user_id, room_id, thread_id) |
On a side note: Given that I'm still getting Matrix notifications, what is of might be the impact of this issue? I could not judge that. |
The impact is that the code to handle notifications will slow down over time as it processes more and more un-summarized notifications. |
Could you check which background updates are pending? SELECT * FROM background_updates; |
Hmm, surprisingly: synapse=# SELECT * FROM background_updates;
update_name | progress_json | depends_on | ordering
-------------+---------------+------------+----------
(0 rows) I opened the logs again and the error is no longer happening (since about 1h30 after start). |
It should not happen as the needed constraint is now there. If you don't see it for a couple of days I think this is fine to close. |
I have not seen this occurring anymore in the past two days, so it seems it resolved itself. |
Great news---thanks for following up! |
I'm getting the same error. I'm not sure, since which version the problem is present in my case. When I'm updating to 1.71.0 the The background_updates Table is empty.
homeserver-Log:
|
@lsrmg That looks different to the original report. Can you file a new issue for it? |
Description
Synapse 1.69 throws the following error every 30 seconds:
ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification
(For log messages/backtrace, see below.)
I do not remember seeing these log messages when I was on Synapse 1.66, where I just upgraded from.
Steps to reproduce
Homeserver
my own instance
Synapse Version
1.69.0 (on Python 3.9.15)
Installation Method
Docker (matrixdotorg/synapse)
Platform
Installation is based on docker-compose, running on Debian 11 (bullseye).
The installation is not new and thus uses
docker.io/postgres:10-alpine
as the database image as I had no time to migrate it yet.Relevant log output
Anything else that would be useful to know?
No response
The text was updated successfully, but these errors were encountered: