You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 18, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 18, 2026. It is now read-only.
Used to filter out a client's own updates in poll responses
Core query: `WHERE type != 'awareness' AND client_id != %s`
`KEY room_type_date (room,type,date_gmt)`
Covers polling AND cleanup queries
Composite index for `WHERE room = %s AND type = %s AND date_gmt < %s`
Changes needed:
```sql
DROP INDEX room_type,
DROP INDEX room_id,
DROP INDEX room_timestamp,
ADD KEY type_client_id (type,client_id),
ADD KEY room (room,collaboration_id),
ADD KEY room_type_date (room,type,date_gmt),
ADD KEY date_gmt (date_gmt)
```
Activity
josephfusco commentedon Aug 17, 2026
Core needs these indexes because it stores both awareness and CRDT updates in wp_collaboration:
type_client_id: filters awareness by clientroom_type_date: prunes old awareness statesWe delegate awareness to Presence API, so wp_collaboration only holds CRDT updates with no type/client_id filtering.
Decision: Composite storage architecture (Trac #64696 comment:177, wordpress-develop PR #11256) validates this split.