Matrix Synapse

The reference Matrix homeserver. This is the full schema at schema version 72 (the main and state stores together), which is the only complete schema the project publishes; every change after it ships as a delta, so this is the version-72 picture rather than the current one. Synapse declares almost no primary keys and almost no foreign keys: rows are identified by unique indexes and the server keeps them consistent itself.

137 tables · 634 columns · 14 foreign keys · 14 domains | 21 errors · 28 warnings · 123 notes

Generated from synapse@v1.160.0.sql on 2026-09-05.

Conventions

Row identity comes from unique indexes, not declared primary keys. 88 of the 109 tables the reviewer flags carry one; the remaining 21 are append-only streams, edge tables and queues with no uniqueness enforced at all.
Relationships are not declared as foreign keys. Only 14 exist across 137 tables; the rest are joins by convention on user_id, room_id, event_id and stream_ordering.
Ordering is by monotonic stream_ordering / stream_id columns rather than timestamps, so workers can resume from a position.
Timestamps are bigint milliseconds since the epoch (ts, created_ts, expiry_time_ms), not timestamptz.
Text columns holding a Matrix type (events.type, event_relations.relation_type) are open namespaces defined by the Matrix specification, not closed enumerations.

Conventions are claims. Findings below are where the schema breaks them.

Findings

Errors (21)

F008current_state_delta_streamprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE current_state_delta_stream ADD PRIMARY KEY (...);

F010deleted_pushersprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE deleted_pushers ADD PRIMARY KEY (...);

F011device_auth_providersprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE device_auth_providers ADD PRIMARY KEY (...);

F012device_federation_inboxprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE device_federation_inbox ADD PRIMARY KEY (...);

F013device_federation_outboxprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE device_federation_outbox ADD PRIMARY KEY (...);

F014device_inboxprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE device_inbox ADD PRIMARY KEY (...);

F017device_lists_outbound_pokesprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE device_lists_outbound_pokes ADD PRIMARY KEY (...);

F021device_lists_streamprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE device_lists_stream ADD PRIMARY KEY (...);

F024e2e_cross_signing_signaturesprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE e2e_cross_signing_signatures ADD PRIMARY KEY (...);

F031event_authprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE event_auth ADD PRIMARY KEY (...);

F032event_auth_chain_linksprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE event_auth_chain_links ADD PRIMARY KEY (...);

F038event_push_actions_stagingprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE event_push_actions_staging ADD PRIMARY KEY (...);

F050insertion_event_edgesprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE insertion_event_edges ADD PRIMARY KEY (...);

F056local_media_repository_url_cacheprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE local_media_repository_url_cache ADD PRIMARY KEY (...);

F061presence_streamprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE presence_stream ADD PRIMARY KEY (...);

F063push_rules_streamprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE push_rules_stream ADD PRIMARY KEY (...);

F074room_alias_serversprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE room_alias_servers ADD PRIMARY KEY (...);

F109state_groups_stateprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE state_groups_state ADD PRIMARY KEY (...);

F087stream_ordering_to_extermprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE stream_ordering_to_exterm ADD PRIMARY KEY (...);

F093user_daily_visitsprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE user_daily_visits ADD PRIMARY KEY (...);

F105users_pending_deactivationprimary-key

No primary key

Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.

Fix Add a natural composite key or a surrogate id.

ALTER TABLE users_pending_deactivation ADD PRIMARY KEY (...);

Warnings (28)

F110access_tokens refresh_token_idfk-index

Foreign key without index

PostgreSQL does not index FK columns automatically. Every DELETE/UPDATE on refresh_tokens must scan access_tokens to check the constraint, and every join from the parent side is a sequential scan. The scan cost grows with the child table forever, so this gets worse on its own. An index is not free. Every write to access_tokens maintains it — insert, update and delete alike — and it takes disk. Weigh that against how often refresh_tokens rows are actually deleted or re-keyed — if the answer is never, the scan never happens and the index only costs.

Fix Add a partial index, scoped to the rows that have a value. refresh_token_id is nullable, so the NULL rows are not indexed at all and the write cost is a fraction of a full index, while the constraint check still uses it.

CREATE INDEX CONCURRENTLY idx_access_tokens_refresh_token_id ON access_tokens(refresh_token_id) WHERE refresh_token_id IS NOT NULL;

F115account_data account_data_typeundocumented-enum

Enum-like column with no CHECK

account_data_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE account_data ADD CONSTRAINT account_data_account_data_type_check CHECK (account_data_type IN (...));

F116application_services_state stateundocumented-enum

Enum-like column with no CHECK

state is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE application_services_state ADD CONSTRAINT application_services_state_state_check CHECK (state IN (...));

F117current_state_delta_stream typeundocumented-enum

Enum-like column with no CHECK

type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE current_state_delta_stream ADD CONSTRAINT current_state_delta_stream_type_check CHECK (type IN (...));

F118current_state_events typeundocumented-enum

Enum-like column with no CHECK

type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE current_state_events ADD CONSTRAINT current_state_events_type_check CHECK (type IN (...));

F119event_auth_chain_to_calculate typeundocumented-enum

Enum-like column with no CHECK

type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE event_auth_chain_to_calculate ADD CONSTRAINT event_auth_chain_to_calculate_type_check CHECK (type IN (...));

F120event_relations relation_typeundocumented-enum

Enum-like column with no CHECK

relation_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE event_relations ADD CONSTRAINT event_relations_relation_type_check CHECK (relation_type IN (...));

F111event_txn_id token_idfk-index

Foreign key without index

PostgreSQL does not index FK columns automatically. Every DELETE/UPDATE on access_tokens must scan event_txn_id to check the constraint, and every join from the parent side is a sequential scan. The scan cost grows with the child table forever, so this gets worse on its own. An index is not free. Every write to event_txn_id maintains it — insert, update and delete alike — and it takes disk. Weigh that against how often access_tokens rows are actually deleted or re-keyed — if the answer is never, the scan never happens and the index only costs.

Fix Add an index on the FK column(s).

CREATE INDEX CONCURRENTLY idx_event_txn_id_token_id ON event_txn_id(token_id);

F121events typeundocumented-enum

Enum-like column with no CHECK

type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE events ADD CONSTRAINT events_type_check CHECK (type IN (...));

F122federation_stream_position typeundocumented-enum

Enum-like column with no CHECK

type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE federation_stream_position ADD CONSTRAINT federation_stream_position_type_check CHECK (type IN (...));

F123local_media_repository media_typeundocumented-enum

Enum-like column with no CHECK

media_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE local_media_repository ADD CONSTRAINT local_media_repository_media_type_check CHECK (media_type IN (...));

F124local_media_repository_thumbnails thumbnail_typeundocumented-enum

Enum-like column with no CHECK

thumbnail_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE local_media_repository_thumbnails ADD CONSTRAINT local_media_repository_thumbnails_thumbnail_type_check CHECK (thumbnail_type IN (...));

F125presence stateundocumented-enum

Enum-like column with no CHECK

state is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE presence ADD CONSTRAINT presence_state_check CHECK (state IN (...));

F126presence_stream stateundocumented-enum

Enum-like column with no CHECK

state is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE presence_stream ADD CONSTRAINT presence_stream_state_check CHECK (state IN (...));

F127pushers kindundocumented-enum

Enum-like column with no CHECK

kind is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE pushers ADD CONSTRAINT pushers_kind_check CHECK (kind IN (...));

F128receipts_graph receipt_typeundocumented-enum

Enum-like column with no CHECK

receipt_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE receipts_graph ADD CONSTRAINT receipts_graph_receipt_type_check CHECK (receipt_type IN (...));

F129receipts_linearized receipt_typeundocumented-enum

Enum-like column with no CHECK

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE receipts_linearized ADD CONSTRAINT receipts_linearized_receipt_type_check CHECK (receipt_type IN (...));

F130remote_media_cache media_typeundocumented-enum

Enum-like column with no CHECK

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE remote_media_cache ADD CONSTRAINT remote_media_cache_media_type_check CHECK (media_type IN (...));

F131remote_media_cache_thumbnails thumbnail_typeundocumented-enum

Enum-like column with no CHECK

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE remote_media_cache_thumbnails ADD CONSTRAINT remote_media_cache_thumbnails_thumbnail_type_check CHECK (thumbnail_type IN (...));

F132room_account_data account_data_typeundocumented-enum

Enum-like column with no CHECK

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE room_account_data ADD CONSTRAINT room_account_data_account_data_type_check CHECK (account_data_type IN (...));

F133room_stats_state history_visibilityundocumented-enum

Enum-like column with no CHECK

history_visibility is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE room_stats_state ADD CONSTRAINT room_stats_state_history_visibility_check CHECK (history_visibility IN (...));

F134room_stats_state room_typeundocumented-enum

Enum-like column with no CHECK

room_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE room_stats_state ADD CONSTRAINT room_stats_state_room_type_check CHECK (room_type IN (...));

F135sessions session_typeundocumented-enum

Enum-like column with no CHECK

session_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE sessions ADD CONSTRAINT sessions_session_type_check CHECK (session_type IN (...));

F136state_events typeundocumented-enum

Enum-like column with no CHECK

type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE state_events ADD CONSTRAINT state_events_type_check CHECK (type IN (...));

F137state_events prev_stateundocumented-enum

Enum-like column with no CHECK

prev_state is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE state_events ADD CONSTRAINT state_events_prev_state_check CHECK (prev_state IN (...));

F140state_groups_state typeundocumented-enum

Enum-like column with no CHECK

type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE state_groups_state ADD CONSTRAINT state_groups_state_type_check CHECK (type IN (...));

F138ui_auth_sessions_credentials stage_typeundocumented-enum

Enum-like column with no CHECK

stage_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE ui_auth_sessions_credentials ADD CONSTRAINT ui_auth_sessions_credentials_stage_type_check CHECK (stage_type IN (...));

F139users user_typeundocumented-enum

Enum-like column with no CHECK

user_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Fix Add a CHECK constraint (cheap, easy to evolve) or a lookup table if values need metadata. Avoid native ENUM types unless the set is truly frozen.

ALTER TABLE users ADD CONSTRAINT users_user_type_check CHECK (user_type IN (...));

Notes (123)

F112access_tokens refresh_token_idfk-nullable

Nullable foreign key

access_tokens.refresh_token_id may be NULL, so the relationship to refresh_tokens is optional. That is legitimate (e.g. approved_by before approval) but often a modelling shrug: a row with no owner, or two nullable FKs that are secretly an either/or.

Fix Confirm the optionality is a domain rule; document it in the column comment.

F145account_dataorphan-table

Isolated table

account_data references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F146account_validityorphan-table

Isolated table

account_validity references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F147application_services_stateorphan-table

Isolated table

application_services_state references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F148application_services_txnsorphan-table

Isolated table

application_services_txns references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F149appservice_room_listorphan-table

Isolated table

appservice_room_list references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F150appservice_stream_positionorphan-table

Isolated table

appservice_stream_position references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F151batch_eventsorphan-table

Isolated table

batch_events references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F152blocked_roomsorphan-table

Isolated table

blocked_rooms references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F153cache_invalidation_stream_by_instanceorphan-table

Isolated table

cache_invalidation_stream_by_instance references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F154current_state_delta_streamorphan-table

Isolated table

current_state_delta_stream references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F155current_state_eventsorphan-table

Isolated table

current_state_events references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F156dehydrated_devicesorphan-table

Isolated table

dehydrated_devices references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F157deleted_pushersorphan-table

Isolated table

deleted_pushers references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F158device_auth_providersorphan-table

Isolated table

device_auth_providers references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F159device_federation_inboxorphan-table

Isolated table

device_federation_inbox references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F160device_federation_outboxorphan-table

Isolated table

device_federation_outbox references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F161device_inboxorphan-table

Isolated table

device_inbox references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F162device_lists_changes_in_roomorphan-table

Isolated table

device_lists_changes_in_room references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F163device_lists_outbound_last_successorphan-table

Isolated table

device_lists_outbound_last_success references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F164device_lists_outbound_pokesorphan-table

Isolated table

device_lists_outbound_pokes references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F165device_lists_remote_cacheorphan-table

Isolated table

device_lists_remote_cache references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F166device_lists_remote_extremetiesorphan-table

Isolated table

device_lists_remote_extremeties references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F167device_lists_remote_resyncorphan-table

Isolated table

device_lists_remote_resync references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F168device_lists_streamorphan-table

Isolated table

device_lists_stream references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F169devicesorphan-table

Isolated table

devices references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F170e2e_cross_signing_keysorphan-table

Isolated table

e2e_cross_signing_keys references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F171e2e_cross_signing_signaturesorphan-table

Isolated table

e2e_cross_signing_signatures references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F172e2e_device_keys_jsonorphan-table

Isolated table

e2e_device_keys_json references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F173e2e_fallback_keys_jsonorphan-table

Isolated table

e2e_fallback_keys_json references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F174e2e_one_time_keys_jsonorphan-table

Isolated table

e2e_one_time_keys_json references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F175e2e_room_keysorphan-table

Isolated table

e2e_room_keys references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F176e2e_room_keys_versionsorphan-table

Isolated table

e2e_room_keys_versions references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F177erased_usersorphan-table

Isolated table

erased_users references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F178event_authorphan-table

Isolated table

event_auth references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F179event_auth_chain_linksorphan-table

Isolated table

event_auth_chain_links references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F180event_auth_chain_to_calculateorphan-table

Isolated table

event_auth_chain_to_calculate references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F181event_auth_chainsorphan-table

Isolated table

event_auth_chains references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F182event_backward_extremitiesorphan-table

Isolated table

event_backward_extremities references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F183event_expiryorphan-table

Isolated table

event_expiry references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F184event_forward_extremitiesorphan-table

Isolated table

event_forward_extremities references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F185event_jsonorphan-table

Isolated table

event_json references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F186event_labelsorphan-table

Isolated table

event_labels references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F187event_push_actionsorphan-table

Isolated table

event_push_actions references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F188event_push_actions_stagingorphan-table

Isolated table

event_push_actions_staging references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F189event_push_summaryorphan-table

Isolated table

event_push_summary references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F190event_push_summary_last_receipt_stream_idorphan-table

Isolated table

event_push_summary_last_receipt_stream_id references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F191event_push_summary_stream_orderingorphan-table

Isolated table

event_push_summary_stream_ordering references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F192event_relationsorphan-table

Isolated table

event_relations references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F193event_reportsorphan-table

Isolated table

event_reports references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F194event_searchorphan-table

Isolated table

event_search references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F195event_to_state_groupsorphan-table

Isolated table

event_to_state_groups references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F196ex_outlier_streamorphan-table

Isolated table

ex_outlier_stream references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F197federation_inbound_events_stagingorphan-table

Isolated table

federation_inbound_events_staging references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F198federation_stream_positionorphan-table

Isolated table

federation_stream_position references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F199ignored_usersorphan-table

Isolated table

ignored_users references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F200insertion_event_edgesorphan-table

Isolated table

insertion_event_edges references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F201insertion_event_extremitiesorphan-table

Isolated table

insertion_event_extremities references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F202insertion_eventsorphan-table

Isolated table

insertion_events references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F203instance_maporphan-table

Isolated table

instance_map references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F204local_current_membershiporphan-table

Isolated table

local_current_membership references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F205local_media_repositoryorphan-table

Isolated table

local_media_repository references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F206local_media_repository_thumbnailsorphan-table

Isolated table

local_media_repository_thumbnails references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F207local_media_repository_url_cacheorphan-table

Isolated table

local_media_repository_url_cache references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F208monthly_active_usersorphan-table

Isolated table

monthly_active_users references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F209open_id_tokensorphan-table

Isolated table

open_id_tokens references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F210presenceorphan-table

Isolated table

presence references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F211presence_streamorphan-table

Isolated table

presence_stream references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F212profilesorphan-table

Isolated table

profiles references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F213push_rulesorphan-table

Isolated table

push_rules references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F214push_rules_enableorphan-table

Isolated table

push_rules_enable references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F215push_rules_streamorphan-table

Isolated table

push_rules_stream references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F216pusher_throttleorphan-table

Isolated table

pusher_throttle references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F217pushersorphan-table

Isolated table

pushers references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F218ratelimit_overrideorphan-table

Isolated table

ratelimit_override references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F219receipts_graphorphan-table

Isolated table

receipts_graph references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F220receipts_linearizedorphan-table

Isolated table

receipts_linearized references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F221received_transactionsorphan-table

Isolated table

received_transactions references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F222redactionsorphan-table

Isolated table

redactions references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F113refresh_tokens next_token_idfk-nullable

Nullable foreign key

refresh_tokens.next_token_id may be NULL, so the relationship to refresh_tokens is optional. That is legitimate (e.g. approved_by before approval) but often a modelling shrug: a row with no owner, or two nullable FKs that are secretly an either/or.

Fix Confirm the optionality is a domain rule; document it in the column comment.

F223registration_tokensorphan-table

Isolated table

registration_tokens references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F224rejectionsorphan-table

Isolated table

rejections references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F225remote_media_cacheorphan-table

Isolated table

remote_media_cache references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F226remote_media_cache_thumbnailsorphan-table

Isolated table

remote_media_cache_thumbnails references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F227room_account_dataorphan-table

Isolated table

room_account_data references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F228room_alias_serversorphan-table

Isolated table

room_alias_servers references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F229room_aliasesorphan-table

Isolated table

room_aliases references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F230room_depthorphan-table

Isolated table

room_depth references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F231room_membershipsorphan-table

Isolated table

room_memberships references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F232room_retentionorphan-table

Isolated table

room_retention references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F233room_stats_currentorphan-table

Isolated table

room_stats_current references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F234room_stats_earliest_tokenorphan-table

Isolated table

room_stats_earliest_token references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F235room_stats_stateorphan-table

Isolated table

room_stats_state references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F236room_tagsorphan-table

Isolated table

room_tags references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F237room_tags_revisionsorphan-table

Isolated table

room_tags_revisions references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F238server_keys_jsonorphan-table

Isolated table

server_keys_json references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F239server_signature_keysorphan-table

Isolated table

server_signature_keys references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F240sessionsorphan-table

Isolated table

sessions references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F241state_eventsorphan-table

Isolated table

state_events references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F263state_group_edgesorphan-table

Isolated table

state_group_edges references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F264state_groupsorphan-table

Isolated table

state_groups references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F265state_groups_stateorphan-table

Isolated table

state_groups_state references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F242stats_incremental_positionorphan-table

Isolated table

stats_incremental_position references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F243stream_ordering_to_extermorphan-table

Isolated table

stream_ordering_to_exterm references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F244stream_positionsorphan-table

Isolated table

stream_positions references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F245threepid_guest_access_tokensorphan-table

Isolated table

threepid_guest_access_tokens references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F246threepid_validation_sessionorphan-table

Isolated table

threepid_validation_session references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F247threepid_validation_tokenorphan-table

Isolated table

threepid_validation_token references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F248user_daily_visitsorphan-table

Isolated table

user_daily_visits references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F249user_directoryorphan-table

Isolated table

user_directory references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F250user_directory_searchorphan-table

Isolated table

user_directory_search references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F251user_directory_stream_posorphan-table

Isolated table

user_directory_stream_pos references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F252user_external_idsorphan-table

Isolated table

user_external_ids references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F253user_filtersorphan-table

Isolated table

user_filters references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F254user_ipsorphan-table

Isolated table

user_ips references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F255user_signature_streamorphan-table

Isolated table

user_signature_stream references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F256user_stats_currentorphan-table

Isolated table

user_stats_current references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F257user_threepid_id_serverorphan-table

Isolated table

user_threepid_id_server references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F258user_threepidsorphan-table

Isolated table

user_threepids references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F259users_in_public_roomsorphan-table

Isolated table

users_in_public_rooms references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F260users_pending_deactivationorphan-table

Isolated table

users_pending_deactivation references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F261users_who_share_private_roomsorphan-table

Isolated table

users_who_share_private_rooms references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

F262worker_locksorphan-table

Isolated table

worker_locks references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Fix Document its purpose or drop it.

Schema

137 tables · 14 foreign keys · 14 domains. Open the 3D explorer: rotate, zoom, click any table or relationship.

Accounts and identity 14 tables

Local accounts, profiles, third-party identifiers (email and phone), registration tokens, and the flags for deactivated or erased users.

Relationships

No foreign keys in this domain.

users

13 cols · no RLS · line 943View in 3D

Enum-like column with no CHECK user_type — user_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Column	Type	Null	Default
`name` UK	text	null
`password_hash`	text	null
`creation_ts`	bigint	null
`admin`	smallint	NOT NULL	0
`upgrade_ts`	bigint	null
`is_guest`	smallint	NOT NULL	0
`appservice_id`	text	null
`consent_version`	text	null
`consent_server_notice_sent`	text	null
`user_type`	text	null
`deactivated`	smallint	NOT NULL	0
`shadow_banned`	boolean	null
`consent_ts`	bigint	null

Indexes

(creation_ts) users_creation_ts

Referenced by

users_to_send_full_presence_to (user_id, 1:1)

profiles

3 cols · no RLS · line 568View in 3D

Isolated table — profiles references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id` UK	text	NOT NULL
`displayname`	text	null
`avatar_url`	text	null

Indexes

none

Referenced by

nothing

user_external_ids

3 cols · no RLS · line 896View in 3D

Isolated table — user_external_ids references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`auth_provider`	text	NOT NULL
`external_id`	text	NOT NULL
`user_id`	text	NOT NULL

Indexes

(user_id) user_external_ids_user_id_idx

Referenced by

nothing

user_threepids

5 cols · no RLS · line 936View in 3D

Isolated table — user_threepids references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`medium`	text	NOT NULL
`address`	text	NOT NULL
`validated_at`	bigint	NOT NULL
`added_at`	bigint	NOT NULL

Indexes

(medium, address) user_threepids_medium_address
(user_id) user_threepids_user_id

Referenced by

nothing

user_threepid_id_server

4 cols · no RLS · line 930View in 3D

Isolated table — user_threepid_id_server references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`medium`	text	NOT NULL
`address`	text	NOT NULL
`id_server`	text	NOT NULL

Indexes

UNIQUE (user_id, medium, address, id_server) user_threepid_id_server_idx

Referenced by

nothing

threepid_validation_session

6 cols · no RLS · line 842View in 3D

Isolated table — threepid_validation_session references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`session_id` PK	text	NOT NULL
`medium`	text	NOT NULL
`address`	text	NOT NULL
`client_secret`	text	NOT NULL
`last_send_attempt`	bigint	NOT NULL
`validated_at`	bigint	null

Indexes

none

Referenced by

nothing

threepid_validation_token

4 cols · no RLS · line 850View in 3D

Isolated table — threepid_validation_token references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`token` PK	text	NOT NULL
`session_id`	text	NOT NULL
`next_link`	text	null
`expires`	bigint	NOT NULL

Indexes

(session_id) threepid_validation_token_session_id

Referenced by

nothing

threepid_guest_access_tokens

4 cols · no RLS · line 836View in 3D

Isolated table — threepid_guest_access_tokens references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`medium`	text	null
`address`	text	null
`guest_access_token`	text	null
`first_inviter`	text	null

Indexes

UNIQUE (medium, address) threepid_guest_access_tokens_index

Referenced by

nothing

erased_users

1 cols · no RLS · line 271View in 3D

Isolated table — erased_users references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`user_id`	text	NOT NULL

Indexes

UNIQUE (user_id) erased_users_user

Referenced by

nothing

users_pending_deactivation

1 cols · no RLS · line 962View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — users_pending_deactivation references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`user_id`	text	NOT NULL

Indexes

none

Referenced by

nothing

account_validity

5 cols · no RLS · line 40View in 3D

Isolated table — account_validity references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id` PK	text	NOT NULL
`expiration_ts_ms`	bigint	NOT NULL
`email_sent`	boolean	NOT NULL
`renewal_token`	text	null
`token_used_ts_ms`	bigint	null

Indexes

none

Referenced by

nothing

registration_tokens

5 cols · no RLS · line 675View in 3D

Isolated table — registration_tokens references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`token` UK	text	NOT NULL
`uses_allowed`	integer	null
`pending`	integer	NOT NULL
`completed`	integer	NOT NULL
`expiry_time`	bigint	null

Indexes

none

Referenced by

nothing

user_filters

3 cols · no RLS · line 901View in 3D

Isolated table — user_filters references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`filter_id`	bigint	NOT NULL
`filter_json`	bytea	NOT NULL

Indexes

UNIQUE (user_id, filter_id) user_filters_unique

Referenced by

nothing

ignored_users

2 cols · no RLS · line 460View in 3D

Isolated table — ignored_users references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`ignorer_user_id`	text	NOT NULL
`ignored_user_id`	text	NOT NULL

Indexes

(ignored_user_id) ignored_users_ignored_user_id
UNIQUE (ignorer_user_id, ignored_user_id) ignored_users_uniqueness

Referenced by

nothing

Sessions and tokens 8 tables

How a client proves who it is: access and refresh tokens, OpenID tokens, and the multi-stage interactive auth sessions used for login and account changes.

Relationships

access_tokens.refresh_token_id → refresh_tokens.id — one refresh_tokens, many access_tokens · optional · ON DELETE CASCADE · not indexed
why: not documented
refresh_tokens.next_token_id → refresh_tokens.id — one refresh_tokens, many refresh_tokens · optional · ON DELETE CASCADE · indexed
why: not documented
ui_auth_sessions_credentials.session_id → ui_auth_sessions.session_id — one ui_auth_sessions, many ui_auth_sessions_credentials · required · ON DELETE NO ACTION · indexed
why: not documented
ui_auth_sessions_ips.session_id → ui_auth_sessions.session_id — one ui_auth_sessions, many ui_auth_sessions_ips · required · ON DELETE NO ACTION · indexed
why: not documented

access_tokens

9 cols · no RLS · line 16View in 3D

Foreign key without index refresh_token_id — PostgreSQL does not index FK columns automatically. Every DELETE/UPDATE on refresh_tokens must scan access_tokens to check the constraint, and every join from the parent side is a sequential scan. The scan cost grows with the child table forever, so this gets worse on its own. An index is not free. Every write to access_tokens maintains it — insert, update and delete alike — and it takes disk. Weigh that against how often refresh_tokens rows are actually deleted or re-keyed — if the answer is never, the scan never happens and the index only costs.
Nullable foreign key refresh_token_id — access_tokens.refresh_token_id may be NULL, so the relationship to refresh_tokens is optional. That is legitimate (e.g. approved_by before approval) but often a modelling shrug: a row with no owner, or two nullable FKs that are secretly an either/or.

Column	Type	Null	References
`id` PK	bigint	NOT NULL
`user_id`	text	NOT NULL
`device_id`	text	null
`token` UK	text	NOT NULL
`valid_until_ms`	bigint	null
`puppets_user_id`	text	null
`last_validated`	bigint	null
`refresh_token_id`	bigint	null	refresh_tokens.id 1:N · CASCADE
`used`	boolean	null

Indexes

(user_id, device_id) access_tokens_device_id

Referenced by

event_txn_id (token_id, 1:N)

refresh_tokens

7 cols · no RLS · line 666View in 3D

Nullable foreign key next_token_id — refresh_tokens.next_token_id may be NULL, so the relationship to refresh_tokens is optional. That is legitimate (e.g. approved_by before approval) but often a modelling shrug: a row with no owner, or two nullable FKs that are secretly an either/or.

Column	Type	Null	References
`id` PK	bigint	NOT NULL
`user_id`	text	NOT NULL
`device_id`	text	NOT NULL
`token` UK	text	NOT NULL
`next_token_id`	bigint	null	refresh_tokens.id 1:N · CASCADE
`expiry_ts`	bigint	null
`ultimate_session_expiry_ts`	bigint	null

Indexes

(next_token_id) WHERE next_token_id IS NOT NULL refresh_tokens_next_token_id

Referenced by

access_tokens (refresh_token_id, 1:N)
refresh_tokens (next_token_id, 1:N)

open_id_tokens

3 cols · no RLS · line 529View in 3D

Isolated table — open_id_tokens references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`token` PK	text	NOT NULL
`ts_valid_until_ms`	bigint	NOT NULL
`user_id`	text	NOT NULL

Indexes

(ts_valid_until_ms) open_id_tokens_ts_valid_until_ms

Referenced by

nothing

ui_auth_sessions

7 cols · no RLS · line 856View in 3D

Column	Type	Null
`session_id` UK	text	NOT NULL
`creation_time`	bigint	NOT NULL
`serverdict`	text	NOT NULL
`clientdict`	text	NOT NULL
`uri`	text	NOT NULL
`method`	text	NOT NULL
`description`	text	NOT NULL

Indexes

none

Referenced by

ui_auth_sessions_credentials (session_id, 1:N)
ui_auth_sessions_ips (session_id, 1:N)

ui_auth_sessions_credentials

3 cols · no RLS · line 865View in 3D

Enum-like column with no CHECK stage_type — stage_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Column	Type	Null	References
`session_id`	text	NOT NULL	ui_auth_sessions.session_id 1:N
`stage_type`	text	NOT NULL
`result`	text	NOT NULL

Indexes

none

Referenced by

nothing

ui_auth_sessions_ips

3 cols · no RLS · line 870View in 3D

Column	Type	Null	References
`session_id`	text	NOT NULL	ui_auth_sessions.session_id 1:N
`ip`	text	NOT NULL
`user_agent`	text	NOT NULL

Indexes

none

Referenced by

nothing

sessions

4 cols · no RLS · line 808View in 3D

Enum-like column with no CHECK session_type — session_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — sessions references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`session_type`	text	NOT NULL
`session_id`	text	NOT NULL
`value`	text	NOT NULL
`expiry_time_ms`	bigint	NOT NULL

Indexes

none

Referenced by

nothing

device_auth_providers

4 cols · no RLS · line 137View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — device_auth_providers references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`device_id`	text	NOT NULL
`auth_provider_id`	text	NOT NULL
`auth_provider_session_id`	text	NOT NULL

Indexes

(user_id, device_id) device_auth_providers_devices
(auth_provider_id, auth_provider_session_id) device_auth_providers_sessions

Referenced by

nothing

Devices and device lists 12 tables

One row per logged-in device, the to-device message inbox, and the machinery that tells other servers when a user's device list changes.

Relationships

No foreign keys in this domain.

devices

7 cols · no RLS · line 209View in 3D

Isolated table — devices references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default
`user_id`	text	NOT NULL
`device_id`	text	NOT NULL
`display_name`	text	null
`last_seen`	bigint	null
`ip`	text	null
`user_agent`	text	null
`hidden`	boolean	null	FALSE

Indexes

none

Referenced by

nothing

dehydrated_devices

3 cols · no RLS · line 114View in 3D

Isolated table — dehydrated_devices references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id` PK	text	NOT NULL
`device_id`	text	NOT NULL
`device_data`	text	NOT NULL

Indexes

none

Referenced by

nothing

device_inbox

5 cols · no RLS · line 156View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — device_inbox references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`device_id`	text	NOT NULL
`stream_id`	bigint	NOT NULL
`message_json`	text	NOT NULL
`instance_name`	text	null

Indexes

(stream_id, user_id) device_inbox_stream_id_user_id
(user_id, device_id, stream_id) device_inbox_user_stream_id

Referenced by

nothing

device_lists_stream

3 cols · no RLS · line 204View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — device_lists_stream references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`stream_id`	bigint	NOT NULL
`user_id`	text	NOT NULL
`device_id`	text	NOT NULL

Indexes

(stream_id, user_id) device_lists_stream_id
(user_id, device_id) device_lists_stream_user_id

Referenced by

nothing

device_lists_changes_in_room

6 cols · no RLS · line 169View in 3D

Isolated table — device_lists_changes_in_room references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`device_id`	text	NOT NULL
`room_id`	text	NOT NULL
`stream_id`	bigint	NOT NULL
`converted_to_destinations`	boolean	NOT NULL
`opentracing_context`	text	null

Indexes

UNIQUE (stream_id, room_id) device_lists_changes_in_stream_id
(stream_id) WHERE NOT converted_to_destinations device_lists_changes_in_stream_id_unconverted

Referenced by

nothing

device_lists_outbound_pokes

7 cols · no RLS · line 182View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — device_lists_outbound_pokes references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`destination`	text	NOT NULL
`stream_id`	bigint	NOT NULL
`user_id`	text	NOT NULL
`device_id`	text	NOT NULL
`sent`	boolean	NOT NULL
`ts`	bigint	NOT NULL
`opentracing_context`	text	null

Indexes

(destination, stream_id) device_lists_outbound_pokes_id
(stream_id) device_lists_outbound_pokes_stream
(destination, user_id) device_lists_outbound_pokes_user

Referenced by

nothing

device_lists_outbound_last_success

3 cols · no RLS · line 177View in 3D

Isolated table — device_lists_outbound_last_success references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`destination`	text	NOT NULL
`user_id`	text	NOT NULL
`stream_id`	bigint	NOT NULL

Indexes

UNIQUE (destination, user_id) device_lists_outbound_last_success_unique_idx

Referenced by

nothing

device_lists_remote_cache

3 cols · no RLS · line 191View in 3D

Isolated table — device_lists_remote_cache references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`device_id`	text	NOT NULL
`content`	text	NOT NULL

Indexes

UNIQUE (user_id, device_id) device_lists_remote_cache_unique_id

Referenced by

nothing

device_lists_remote_extremeties

2 cols · no RLS · line 196View in 3D

Isolated table — device_lists_remote_extremeties references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`user_id`	text	NOT NULL
`stream_id`	text	NOT NULL

Indexes

UNIQUE (user_id) device_lists_remote_extremeties_unique_idx

Referenced by

nothing

device_lists_remote_resync

2 cols · no RLS · line 200View in 3D

Isolated table — device_lists_remote_resync references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`user_id`	text	NOT NULL
`added_ts`	bigint	NOT NULL

Indexes

UNIQUE (user_id) device_lists_remote_resync_idx
(added_ts) device_lists_remote_resync_ts_idx

Referenced by

nothing

device_federation_inbox

4 cols · no RLS · line 143View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — device_federation_inbox references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`origin`	text	NOT NULL
`message_id`	text	NOT NULL
`received_ts`	bigint	NOT NULL
`instance_name`	text	null

Indexes

(origin, message_id) device_federation_inbox_sender_id

Referenced by

nothing

device_federation_outbox

5 cols · no RLS · line 149View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — device_federation_outbox references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`destination`	text	NOT NULL
`stream_id`	bigint	NOT NULL
`queued_ts`	bigint	NOT NULL
`messages_json`	text	NOT NULL
`instance_name`	text	null

Indexes

(destination, stream_id) device_federation_outbox_destination_id
(stream_id) device_federation_outbox_id

Referenced by

nothing

End-to-end encryption 8 tables

Device keys, one-time and fallback keys, cross-signing keys and signatures, and server-side room key backups.

Relationships

No foreign keys in this domain.

e2e_device_keys_json

4 cols · no RLS · line 231View in 3D

Isolated table — e2e_device_keys_json references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`device_id`	text	NOT NULL
`ts_added_ms`	bigint	NOT NULL
`key_json`	text	NOT NULL

Indexes

none

Referenced by

nothing

e2e_one_time_keys_json

6 cols · no RLS · line 245View in 3D

Isolated table — e2e_one_time_keys_json references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`device_id`	text	NOT NULL
`algorithm`	text	NOT NULL
`key_id`	text	NOT NULL
`ts_added_ms`	bigint	NOT NULL
`key_json`	text	NOT NULL

Indexes

none

Referenced by

nothing

e2e_fallback_keys_json

6 cols · no RLS · line 237View in 3D

Isolated table — e2e_fallback_keys_json references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default
`user_id`	text	NOT NULL
`device_id`	text	NOT NULL
`algorithm`	text	NOT NULL
`key_id`	text	NOT NULL
`key_json`	text	NOT NULL
`used`	boolean	NOT NULL	FALSE

Indexes

none

Referenced by

nothing

e2e_cross_signing_keys

4 cols · no RLS · line 218View in 3D

Isolated table — e2e_cross_signing_keys references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`keytype`	text	NOT NULL
`keydata`	text	NOT NULL
`stream_id`	bigint	NOT NULL

Indexes

UNIQUE (user_id, keytype, stream_id) e2e_cross_signing_keys_idx
UNIQUE (stream_id) e2e_cross_signing_keys_stream_idx

Referenced by

nothing

e2e_cross_signing_signatures

5 cols · no RLS · line 224View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — e2e_cross_signing_signatures references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`key_id`	text	NOT NULL
`target_user_id`	text	NOT NULL
`target_device_id`	text	NOT NULL
`signature`	text	NOT NULL

Indexes

(user_id, target_user_id, target_device_id) e2e_cross_signing_signatures2_idx

Referenced by

nothing

e2e_room_keys

8 cols · no RLS · line 253View in 3D

Isolated table — e2e_room_keys references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`room_id`	text	NOT NULL
`session_id`	text	NOT NULL
`version`	bigint	NOT NULL
`first_message_index`	integer	null
`forwarded_count`	integer	null
`is_verified`	boolean	null
`session_data`	text	NOT NULL

Indexes

UNIQUE (user_id, version, room_id, session_id) e2e_room_keys_with_version_idx

Referenced by

nothing

e2e_room_keys_versions

6 cols · no RLS · line 263View in 3D

Isolated table — e2e_room_keys_versions references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default
`user_id`	text	NOT NULL
`version`	bigint	NOT NULL
`algorithm`	text	NOT NULL
`auth_data`	text	NOT NULL
`deleted`	smallint	NOT NULL	0
`etag`	bigint	null

Indexes

UNIQUE (user_id, version) e2e_room_keys_versions_idx

Referenced by

nothing

user_signature_stream

3 cols · no RLS · line 920View in 3D

Isolated table — user_signature_stream references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`stream_id`	bigint	NOT NULL
`from_user_id`	text	NOT NULL
`user_ids`	text	NOT NULL

Indexes

UNIQUE (stream_id) user_signature_stream_idx

Referenced by

nothing

Rooms and membership 12 tables

Rooms, their aliases, who is in them, per-room tags and account data, retention policy and the server-level block list.

Relationships

No foreign keys in this domain.

rooms

5 cols · no RLS · line 785View in 3D

Column	Type	Null
`room_id` PK	text	NOT NULL
`is_public`	boolean	null
`creator`	text	null
`room_version`	text	null
`has_auth_chain_index`	boolean	null

Indexes

(is_public) public_room_index

Referenced by

destination_rooms (room_id, 1:N)
partial_state_rooms (room_id, 1:1)

room_aliases

3 cols · no RLS · line 720View in 3D

Isolated table — room_aliases references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`room_alias` UK	text	NOT NULL
`room_id`	text	NOT NULL
`creator`	text	null

Indexes

(room_id) room_aliases_id

Referenced by

nothing

room_alias_servers

2 cols · no RLS · line 716View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — room_alias_servers references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`room_alias`	text	NOT NULL
`server`	text	NOT NULL

Indexes

(room_alias) room_alias_servers_alias

Referenced by

nothing

room_memberships

8 cols · no RLS · line 729View in 3D

Isolated table — room_memberships references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default
`event_id` UK	text	NOT NULL
`user_id`	text	NOT NULL
`sender`	text	NOT NULL
`room_id`	text	NOT NULL
`membership`	text	NOT NULL
`forgotten`	integer	null	0
`display_name`	text	null
`avatar_url`	text	null

Indexes

(room_id) room_memberships_room_id
(user_id) room_memberships_user_id
(user_id, room_id) WHERE forgotten = 1 room_memberships_user_room_forgotten

Referenced by

nothing

local_current_membership

4 cols · no RLS · line 490View in 3D

Isolated table — local_current_membership references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`room_id`	text	NOT NULL
`user_id`	text	NOT NULL
`event_id`	text	NOT NULL
`membership`	text	NOT NULL

Indexes

UNIQUE (user_id, room_id) local_current_membership_idx
(room_id) local_current_membership_room_idx

Referenced by

nothing

room_depth

2 cols · no RLS · line 725View in 3D

Isolated table — room_depth references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`room_id` UK	text	NOT NULL
`min_depth`	bigint	null

Indexes

none

Referenced by

nothing

room_retention

4 cols · no RLS · line 739View in 3D

Isolated table — room_retention references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`room_id` PK	text	NOT NULL
`event_id` PK	text	NOT NULL
`min_lifetime`	bigint	null
`max_lifetime`	bigint	null

Indexes

(max_lifetime) room_retention_max_lifetime_idx

Referenced by

nothing

blocked_rooms

2 cols · no RLS · line 81View in 3D

Isolated table — blocked_rooms references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`room_id`	text	NOT NULL
`user_id`	text	NOT NULL

Indexes

UNIQUE (room_id) blocked_rooms_idx

Referenced by

nothing

room_tags

4 cols · no RLS · line 773View in 3D

Isolated table — room_tags references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`room_id`	text	NOT NULL
`tag`	text	NOT NULL
`content`	text	NOT NULL

Indexes

none

Referenced by

nothing

room_tags_revisions

4 cols · no RLS · line 779View in 3D

Isolated table — room_tags_revisions references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`room_id`	text	NOT NULL
`stream_id`	bigint	NOT NULL
`instance_name`	text	null

Indexes

none

Referenced by

nothing

room_account_data

6 cols · no RLS · line 708View in 3D

Enum-like column with no CHECK account_data_type — account_data_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — room_account_data references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`room_id`	text	NOT NULL
`account_data_type`	text	NOT NULL
`stream_id`	bigint	NOT NULL
`content`	text	NOT NULL
`instance_name`	text	null

Indexes

(user_id, stream_id) room_account_data_stream_id

Referenced by

nothing

account_data

5 cols · no RLS · line 27View in 3D

Enum-like column with no CHECK account_data_type — account_data_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — account_data references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`account_data_type`	text	NOT NULL
`stream_id`	bigint	NOT NULL
`content`	text	NOT NULL
`instance_name`	text	null

Indexes

(user_id, stream_id) account_data_stream_id

Referenced by

nothing

The event graph 23 tables

The heart of a homeserver: every event, its JSON, the directed acyclic graph edges that order it, the authorisation chains, and the extremities that mark the current frontier.

Relationships

event_edges.event_id → events.event_id — one events, many event_edges · required · ON DELETE NO ACTION · indexed
why: not documented
event_txn_id.event_id → events.event_id — one events, at most one event_txn_id · required · ON DELETE CASCADE · indexed
why: not documented
event_txn_id.token_id → access_tokens.id — one access_tokens, many event_txn_id · required · ON DELETE CASCADE · not indexed
why: not documented

events

17 cols · no RLS · line 410View in 3D

Enum-like column with no CHECK type — type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.

Column	Type	Null	Default
`topological_ordering`	bigint	NOT NULL
`event_id` UK	text	NOT NULL
`type`	text	NOT NULL
`room_id`	text	NOT NULL
`content`	text	null
`unrecognized_keys`	text	null
`processed`	boolean	NOT NULL
`outlier`	boolean	NOT NULL
`depth`	bigint	NOT NULL	0
`origin_server_ts`	bigint	null
`received_ts`	bigint	null
`sender`	text	null
`contains_url`	boolean	null
`instance_name`	text	null
`stream_ordering`	bigint	null
`state_key`	text	null
`rejection_reason`	text	null

Indexes

(room_id, topological_ordering, stream_ordering) WHERE contains_url = TRUE AND outlier = FALSE event_contains_url_index
(room_id, topological_ordering, stream_ordering) events_order_room
(room_id, stream_ordering) events_room_stream
UNIQUE (stream_ordering) events_stream_ordering
(origin_server_ts, stream_ordering) events_ts

Referenced by

event_edges (event_id, 1:N)
event_txn_id (event_id, 1:1)
partial_state_events (event_id, 1:1)

event_json

5 cols · no RLS · line 320View in 3D

Isolated table — event_json references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`event_id` UK	text	NOT NULL
`room_id`	text	NOT NULL
`internal_metadata`	text	NOT NULL
`json`	text	NOT NULL
`format_version`	integer	null

Indexes

none

Referenced by

nothing

event_edges

4 cols · no RLS · line 306View in 3D

Column	Type	Null	Default	References
`event_id`	text	NOT NULL		events.event_id 1:N
`prev_event_id`	text	NOT NULL
`room_id`	text	null
`is_state`	boolean	NOT NULL	FALSE

Indexes

(prev_event_id) ev_edges_prev_id
UNIQUE (event_id, prev_event_id) event_edges_event_id_prev_event_id_idx

Referenced by

nothing

event_auth

3 cols · no RLS · line 274View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — event_auth references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`event_id`	text	NOT NULL
`auth_id`	text	NOT NULL
`room_id`	text	NOT NULL

Indexes

(event_id) evauth_edges_id

Referenced by

nothing

event_auth_chains

3 cols · no RLS · line 297View in 3D

Isolated table — event_auth_chains references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`event_id` PK	text	NOT NULL
`chain_id`	bigint	NOT NULL
`sequence_number`	bigint	NOT NULL

Indexes

UNIQUE (chain_id, sequence_number) event_auth_chains_c_seq_index

Referenced by

nothing

event_auth_chain_links

4 cols · no RLS · line 285View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — event_auth_chain_links references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`origin_chain_id`	bigint	NOT NULL
`origin_sequence_number`	bigint	NOT NULL
`target_chain_id`	bigint	NOT NULL
`target_sequence_number`	bigint	NOT NULL

Indexes

(origin_chain_id, target_chain_id) event_auth_chain_links_idx

Referenced by

nothing

event_auth_chain_to_calculate

4 cols · no RLS · line 291View in 3D

Enum-like column with no CHECK type — type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — event_auth_chain_to_calculate references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`event_id` PK	text	NOT NULL
`room_id`	text	NOT NULL
`type`	text	NOT NULL
`state_key`	text	NOT NULL

Indexes

(room_id) event_auth_chain_to_calculate_rm_id

Referenced by

nothing

event_backward_extremities

2 cols · no RLS · line 302View in 3D

Isolated table — event_backward_extremities references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`event_id`	text	NOT NULL
`room_id`	text	NOT NULL

Indexes

(event_id) ev_b_extrem_id
(room_id) ev_b_extrem_room

Referenced by

nothing

event_forward_extremities

2 cols · no RLS · line 316View in 3D

Isolated table — event_forward_extremities references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`event_id`	text	NOT NULL
`room_id`	text	NOT NULL

Indexes

(event_id) ev_extrem_id
(room_id) ev_extrem_room

Referenced by

nothing

event_relations

4 cols · no RLS · line 374View in 3D

Enum-like column with no CHECK relation_type — relation_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — event_relations references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`event_id`	text	NOT NULL
`relates_to_id`	text	NOT NULL
`relation_type`	text	NOT NULL
`aggregation_key`	text	null

Indexes

UNIQUE (event_id) event_relations_id
(relates_to_id, relation_type, aggregation_key) event_relations_relates

Referenced by

nothing

event_labels

4 cols · no RLS · line 327View in 3D

Isolated table — event_labels references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`event_id` PK	text	NOT NULL
`label` PK	text	NOT NULL
`room_id`	text	NOT NULL
`topological_ordering`	bigint	NOT NULL

Indexes

(room_id, label, topological_ordering) event_labels_room_id_label_idx

Referenced by

nothing

event_expiry

2 cols · no RLS · line 312View in 3D

Isolated table — event_expiry references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`event_id` PK	text	NOT NULL
`expiry_ts`	bigint	NOT NULL

Indexes

(expiry_ts) event_expiry_expiry_ts_idx

Referenced by

nothing

event_reports

7 cols · no RLS · line 380View in 3D

Isolated table — event_reports references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`id` PK	bigint	NOT NULL
`received_ts`	bigint	NOT NULL
`room_id`	text	NOT NULL
`event_id`	text	NOT NULL
`user_id`	text	NOT NULL
`reason`	text	null
`content`	text	null

Indexes

none

Referenced by

nothing

event_search

7 cols · no RLS · line 389View in 3D

Isolated table — event_search references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`event_id`	text	null
`room_id`	text	null
`sender`	text	null
`key`	text	null
`vector`	tsvector	null
`origin_server_ts`	bigint	null
`stream_ordering`	bigint	null

Indexes

(room_id) event_search_ev_ridx
UNIQUE (event_id) event_search_event_id_idx
(vector) event_search_fts_idx

Referenced by

nothing

redactions

4 cols · no RLS · line 660View in 3D

Isolated table — redactions references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default
`event_id` UK	text	NOT NULL
`redacts`	text	NOT NULL
`have_censored`	boolean	NOT NULL	FALSE
`received_ts`	bigint	null

Indexes

(received_ts) WHERE NOT have_censored redactions_have_censored_ts
(redacts) redactions_redacts

Referenced by

nothing

rejections

3 cols · no RLS · line 682View in 3D

Isolated table — rejections references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`event_id` UK	text	NOT NULL
`reason`	text	NOT NULL
`last_check`	text	NOT NULL

Indexes

none

Referenced by

nothing

batch_events

3 cols · no RLS · line 76View in 3D

Isolated table — batch_events references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`event_id`	text	NOT NULL
`room_id`	text	NOT NULL
`batch_id`	text	NOT NULL

Indexes

(batch_id) batch_events_batch_id
UNIQUE (event_id) chunk_events_event_id

Referenced by

nothing

insertion_events

3 cols · no RLS · line 473View in 3D

Isolated table — insertion_events references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`event_id`	text	NOT NULL
`room_id`	text	NOT NULL
`next_batch_id`	text	NOT NULL

Indexes

UNIQUE (event_id) insertion_events_event_id
(next_batch_id) insertion_events_next_batch_id

Referenced by

nothing

insertion_event_edges

3 cols · no RLS · line 464View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — insertion_event_edges references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`event_id`	text	NOT NULL
`room_id`	text	NOT NULL
`insertion_prev_event_id`	text	NOT NULL

Indexes

(event_id) insertion_event_edges_event_id
(insertion_prev_event_id) insertion_event_edges_insertion_prev_event_id
(room_id) insertion_event_edges_insertion_room_id

Referenced by

nothing

insertion_event_extremities

2 cols · no RLS · line 469View in 3D

Isolated table — insertion_event_extremities references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`event_id`	text	NOT NULL
`room_id`	text	NOT NULL

Indexes

UNIQUE (event_id) insertion_event_extremities_event_id
(room_id) insertion_event_extremities_room_id

Referenced by

nothing

ex_outlier_stream

4 cols · no RLS · line 441View in 3D

Isolated table — ex_outlier_stream references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`event_stream_ordering` PK	bigint	NOT NULL
`event_id`	text	NOT NULL
`state_group`	bigint	NOT NULL
`instance_name`	text	null

Indexes

none

Referenced by

nothing

stream_ordering_to_exterm

3 cols · no RLS · line 826View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — stream_ordering_to_exterm references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`stream_ordering`	bigint	NOT NULL
`room_id`	text	NOT NULL
`event_id`	text	NOT NULL

Indexes

(stream_ordering) stream_ordering_to_exterm_idx
(room_id, stream_ordering) stream_ordering_to_exterm_rm_idx

Referenced by

nothing

event_txn_id

6 cols · no RLS · line 402View in 3D

Foreign key without index token_id — PostgreSQL does not index FK columns automatically. Every DELETE/UPDATE on access_tokens must scan event_txn_id to check the constraint, and every join from the parent side is a sequential scan. The scan cost grows with the child table forever, so this gets worse on its own. An index is not free. Every write to event_txn_id maintains it — insert, update and delete alike — and it takes disk. Weigh that against how often access_tokens rows are actually deleted or re-keyed — if the answer is never, the scan never happens and the index only costs.

Column	Type	Null	References
`event_id`	text	NOT NULL	events.event_id 1:1 · CASCADE
`room_id`	text	NOT NULL
`user_id`	text	NOT NULL
`token_id`	bigint	NOT NULL	access_tokens.id 1:N · CASCADE
`txn_id`	text	NOT NULL
`inserted_ts`	bigint	NOT NULL

Indexes

UNIQUE (event_id) event_txn_id_event_id
(inserted_ts) event_txn_id_ts
UNIQUE (room_id, user_id, token_id, txn_id) event_txn_id_txn_id

Referenced by

nothing

Room state 7 tables

Resolved room state: state groups and the edges between them, the state each group holds, and the current state of every room.

Relationships

No foreign keys in this domain.

state_groups

3 cols · no RLS · line 1359View in 3D

Isolated table — state_groups references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`id` PK	bigint	NOT NULL
`room_id`	text	NOT NULL
`event_id`	text	NOT NULL

Indexes

(room_id) state_groups_room_id_idx

Referenced by

nothing

state_group_edges

2 cols · no RLS · line 1349View in 3D

synapse/storage/schema/state/full_schemas/72/full.sql.postgres

Isolated table — state_group_edges references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`state_group`	bigint	NOT NULL
`prev_state_group`	bigint	NOT NULL

Indexes

(prev_state_group) state_group_edges_prev_idx
UNIQUE (state_group, prev_state_group) state_group_edges_unique_idx

Referenced by

nothing

state_groups_state

5 cols · no RLS · line 1364View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Enum-like column with no CHECK type — type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — state_groups_state references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`state_group`	bigint	NOT NULL
`room_id`	text	NOT NULL
`type`	text	NOT NULL
`state_key`	text	NOT NULL
`event_id`	text	NOT NULL

Indexes

(state_group, type, state_key) state_groups_state_type_idx

Referenced by

nothing

state_events

5 cols · no RLS · line 814View in 3D

Enum-like column with no CHECK type — type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Enum-like column with no CHECK prev_state — prev_state is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — state_events references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`event_id` UK	text	NOT NULL
`room_id`	text	NOT NULL
`type`	text	NOT NULL
`state_key`	text	NOT NULL
`prev_state`	text	null

Indexes

none

Referenced by

nothing

current_state_events

5 cols · no RLS · line 107View in 3D

Enum-like column with no CHECK type — type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — current_state_events references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`event_id` UK	text	NOT NULL
`room_id`	text	NOT NULL
`type`	text	NOT NULL
`state_key`	text	NOT NULL
`membership`	text	null

Indexes

(state_key) WHERE type = CAST('m.room.member' AS text) current_state_events_member_index

Referenced by

nothing

current_state_delta_stream

7 cols · no RLS · line 98View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Enum-like column with no CHECK type — type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — current_state_delta_stream references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`stream_id`	bigint	NOT NULL
`room_id`	text	NOT NULL
`type`	text	NOT NULL
`state_key`	text	NOT NULL
`event_id`	text	null
`prev_event_id`	text	null
`instance_name`	text	null

Indexes

(stream_id) current_state_delta_stream_idx

Referenced by

nothing

event_to_state_groups

2 cols · no RLS · line 398View in 3D

Isolated table — event_to_state_groups references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`event_id` UK	text	NOT NULL
`state_group`	bigint	NOT NULL

Indexes

(state_group) event_to_state_groups_sg_index

Referenced by

nothing

Federation 10 tables

Talking to other homeservers: destinations and their retry state, received transactions, staged inbound events, remote server signing keys, and partial-state rooms during a fast join.

Relationships

destination_rooms.destination → destinations.destination — one destinations, many destination_rooms · required · ON DELETE NO ACTION · indexed
why: not documented
destination_rooms.room_id → rooms.room_id — one rooms, many destination_rooms · required · ON DELETE NO ACTION · indexed
why: not documented
partial_state_rooms.room_id → rooms.room_id — one rooms, at most one partial_state_rooms · required · ON DELETE NO ACTION · indexed
why: not documented
partial_state_rooms_servers.room_id → partial_state_rooms.room_id — one partial_state_rooms, many partial_state_rooms_servers · required · ON DELETE NO ACTION · indexed
why: not documented
partial_state_events.event_id → events.event_id — one events, at most one partial_state_events · required · ON DELETE NO ACTION · indexed
why: not documented
partial_state_events.room_id → partial_state_rooms.room_id — one partial_state_rooms, many partial_state_events · required · ON DELETE NO ACTION · indexed
why: not documented

destinations

5 cols · no RLS · line 130View in 3D

Column	Type	Null
`destination` PK	text	NOT NULL
`retry_last_ts`	bigint	null
`retry_interval`	bigint	null
`failure_ts`	bigint	null
`last_successful_stream_ordering`	bigint	null

Indexes

none

Referenced by

destination_rooms (destination, 1:N)

destination_rooms

3 cols · no RLS · line 125View in 3D

Column	Type	Null	References
`destination` PK	text	NOT NULL	destinations.destination 1:N
`room_id` PK	text	NOT NULL	rooms.room_id 1:N
`stream_ordering`	bigint	NOT NULL

Indexes

(room_id) destination_rooms_room_id

Referenced by

nothing

received_transactions

6 cols · no RLS · line 652View in 3D

Isolated table — received_transactions references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default
`transaction_id`	text	null
`origin`	text	null
`ts`	bigint	null
`response_code`	integer	null
`response_json`	bytea	null
`has_been_referenced`	smallint	null	0

Indexes

(ts) received_transactions_ts

Referenced by

nothing

federation_inbound_events_staging

6 cols · no RLS · line 447View in 3D

Isolated table — federation_inbound_events_staging references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`origin`	text	NOT NULL
`room_id`	text	NOT NULL
`event_id`	text	NOT NULL
`received_ts`	bigint	NOT NULL
`event_json`	text	NOT NULL
`internal_metadata`	text	NOT NULL

Indexes

UNIQUE (origin, event_id) federation_inbound_events_staging_instance_event
(room_id, received_ts) federation_inbound_events_staging_room

Referenced by

nothing

federation_stream_position

3 cols · no RLS · line 455View in 3D

Enum-like column with no CHECK type — type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — federation_stream_position references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default
`type`	text	NOT NULL
`stream_id`	bigint	NOT NULL
`instance_name`	text	NOT NULL	CAST('master' AS text)

Indexes

UNIQUE (type, instance_name) federation_stream_position_instance

Referenced by

nothing

server_keys_json

6 cols · no RLS · line 792View in 3D

Isolated table — server_keys_json references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`server_name`	text	NOT NULL
`key_id`	text	NOT NULL
`from_server`	text	NOT NULL
`ts_added_ms`	bigint	NOT NULL
`ts_valid_until_ms`	bigint	NOT NULL
`key_json`	bytea	NOT NULL

Indexes

none

Referenced by

nothing

server_signature_keys

6 cols · no RLS · line 800View in 3D

Isolated table — server_signature_keys references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`server_name`	text	null
`key_id`	text	null
`from_server`	text	null
`ts_added_ms`	bigint	null
`verify_key`	bytea	null
`ts_valid_until_ms`	bigint	null

Indexes

none

Referenced by

nothing

partial_state_rooms

1 cols · no RLS · line 538View in 3D

Column	Type	Null	Default	References	Notes
`room_id` PK	text	NOT NULL		rooms.room_id 1:1

Indexes

none

Referenced by

partial_state_events (room_id, 1:N)
partial_state_rooms_servers (room_id, 1:N)

partial_state_rooms_servers

2 cols · no RLS · line 541View in 3D

Column	Type	Null	Default	References	Notes
`room_id`	text	NOT NULL		partial_state_rooms.room_id 1:N
`server_name`	text	NOT NULL

Indexes

none

Referenced by

nothing

partial_state_events

2 cols · no RLS · line 534View in 3D

Column	Type	Null	Default	References	Notes
`room_id`	text	NOT NULL		partial_state_rooms.room_id 1:N
`event_id` UK	text	NOT NULL		events.event_id 1:1

Indexes

(room_id) partial_state_events_room_id_idx

Referenced by

nothing

Application services 4 tables

Bridges and bots: per-service transaction state and the rooms each service has claimed.

Relationships

No foreign keys in this domain.

application_services_state

6 cols · no RLS · line 47View in 3D

Enum-like column with no CHECK state — state is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — application_services_state references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`as_id` PK	text	NOT NULL
`state`	varchar(5)	null
`read_receipt_stream_id`	bigint	null
`presence_stream_id`	bigint	null
`to_device_stream_id`	bigint	null
`device_list_stream_id`	bigint	null

Indexes

none

Referenced by

nothing

application_services_txns

3 cols · no RLS · line 61View in 3D

Isolated table — application_services_txns references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`as_id`	text	NOT NULL
`txn_id`	bigint	NOT NULL
`event_ids`	text	NOT NULL

Indexes

(as_id) application_services_txns_id

Referenced by

nothing

appservice_room_list

3 cols · no RLS · line 66View in 3D

Isolated table — appservice_room_list references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`appservice_id`	text	NOT NULL
`network_id`	text	NOT NULL
`room_id`	text	NOT NULL

Indexes

UNIQUE (appservice_id, network_id, room_id) appservice_room_list_idx

Referenced by

nothing

appservice_stream_position

2 cols · no RLS · line 71View in 3D

Isolated table — appservice_stream_position references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`lock` UK	char(1)	NOT NULL	CAST('X' AS bpchar)		`CHECK lock = CAST('X' AS bpchar)`
`stream_ordering`	bigint	null

Indexes

none

Referenced by

nothing

Table checks: lock = CAST('X' AS bpchar)

Push notifications 11 tables

Registered pushers, the rules deciding what is worth notifying about, and the per-user unread and highlight counts kept alongside them.

Relationships

No foreign keys in this domain.

pushers

15 cols · no RLS · line 605View in 3D

Enum-like column with no CHECK kind — kind is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — pushers references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`id` PK	bigint	NOT NULL
`user_name`	text	NOT NULL
`access_token`	bigint	null
`profile_tag`	text	NOT NULL
`kind`	text	NOT NULL
`app_id`	text	NOT NULL
`app_display_name`	text	NOT NULL
`device_display_name`	text	NOT NULL
`pushkey`	text	NOT NULL
`ts`	bigint	NOT NULL
`lang`	text	null
`data`	text	null
`last_stream_ordering`	bigint	null
`last_success`	bigint	null
`failing_since`	bigint	null

Indexes

none

Referenced by

nothing

deleted_pushers

4 cols · no RLS · line 119View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — deleted_pushers references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`stream_id`	bigint	NOT NULL
`app_id`	text	NOT NULL
`pushkey`	text	NOT NULL
`user_id`	text	NOT NULL

Indexes

(stream_id) deleted_pushers_stream_id

Referenced by

nothing

pusher_throttle

4 cols · no RLS · line 599View in 3D

Isolated table — pusher_throttle references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`pusher` PK	bigint	NOT NULL
`room_id` PK	text	NOT NULL
`last_sent_ts`	bigint	null
`throttle_ms`	bigint	null

Indexes

none

Referenced by

nothing

push_rules

7 cols · no RLS · line 573View in 3D

Isolated table — push_rules references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default
`id` PK	bigint	NOT NULL
`user_name`	text	NOT NULL
`rule_id`	text	NOT NULL
`priority_class`	smallint	NOT NULL
`priority`	integer	NOT NULL	0
`conditions`	text	NOT NULL
`actions`	text	NOT NULL

Indexes

(user_name) push_rules_user_name

Referenced by

nothing

push_rules_enable

4 cols · no RLS · line 582View in 3D

Isolated table — push_rules_enable references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`id` PK	bigint	NOT NULL
`user_name`	text	NOT NULL
`rule_id`	text	NOT NULL
`enabled`	smallint	null

Indexes

(user_name) push_rules_enable_user_name

Referenced by

nothing

push_rules_stream

9 cols · no RLS · line 588View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — push_rules_stream references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`stream_id`	bigint	NOT NULL
`event_stream_ordering`	bigint	NOT NULL
`user_id`	text	NOT NULL
`rule_id`	text	NOT NULL
`op`	text	NOT NULL
`priority_class`	smallint	null
`priority`	integer	null
`conditions`	text	null
`actions`	text	null

Indexes

(stream_id) push_rules_stream_id
(user_id, stream_id) push_rules_stream_user_stream_id

Referenced by

nothing

event_push_actions

11 cols · no RLS · line 333View in 3D

Isolated table — event_push_actions references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`room_id`	text	NOT NULL
`event_id`	text	NOT NULL
`user_id`	text	NOT NULL
`profile_tag`	varchar(32)	null
`actions`	text	NOT NULL
`topological_ordering`	bigint	null
`stream_ordering`	bigint	null
`notif`	smallint	null
`highlight`	smallint	null
`unread`	smallint	null
`thread_id`	text	null

Indexes

(user_id, room_id, topological_ordering, stream_ordering) WHERE highlight = 1 event_push_actions_highlights_index
(user_id, room_id, topological_ordering, stream_ordering) event_push_actions_rm_tokens
(room_id, user_id) event_push_actions_room_id_user_id
(highlight, stream_ordering) WHERE highlight = 0 event_push_actions_stream_highlight_index
(stream_ordering, user_id) event_push_actions_stream_ordering
(user_id, stream_ordering) event_push_actions_u_highlight

Referenced by

nothing

event_push_actions_staging

7 cols · no RLS · line 346View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — event_push_actions_staging references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`event_id`	text	NOT NULL
`user_id`	text	NOT NULL
`actions`	text	NOT NULL
`notif`	smallint	NOT NULL
`highlight`	smallint	NOT NULL
`unread`	smallint	null
`thread_id`	text	null

Indexes

(event_id) event_push_actions_staging_id

Referenced by

nothing

event_push_summary

7 cols · no RLS · line 355View in 3D

Isolated table — event_push_summary references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`room_id`	text	NOT NULL
`notif_count`	bigint	NOT NULL
`stream_ordering`	bigint	NOT NULL
`unread_count`	bigint	null
`last_receipt_stream_ordering`	bigint	null
`thread_id`	text	null

Indexes

UNIQUE (user_id, room_id) event_push_summary_unique_index
UNIQUE (user_id, room_id, thread_id) event_push_summary_unique_index2

Referenced by

nothing

event_push_summary_last_receipt_stream_id

2 cols · no RLS · line 364View in 3D

Isolated table — event_push_summary_last_receipt_stream_id references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`lock` UK	char(1)	NOT NULL	CAST('X' AS bpchar)		`CHECK lock = CAST('X' AS bpchar)`
`stream_id`	bigint	NOT NULL

Indexes

none

Referenced by

nothing

Table checks: lock = CAST('X' AS bpchar)

event_push_summary_stream_ordering

2 cols · no RLS · line 369View in 3D

Isolated table — event_push_summary_stream_ordering references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`lock` UK	char(1)	NOT NULL	CAST('X' AS bpchar)		`CHECK lock = CAST('X' AS bpchar)`
`stream_ordering`	bigint	NOT NULL

Indexes

none

Referenced by

nothing

Table checks: lock = CAST('X' AS bpchar)

Receipts and presence 5 tables

Read receipts in both graph and linearised form, and who is online.

Relationships

users_to_send_full_presence_to.user_id → users.name — one users, at most one users_to_send_full_presence_to · required · ON DELETE NO ACTION · indexed
why: not documented

receipts_graph

6 cols · no RLS · line 627View in 3D

Enum-like column with no CHECK receipt_type — receipt_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — receipts_graph references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`room_id`	text	NOT NULL
`receipt_type`	text	NOT NULL
`user_id`	text	NOT NULL
`event_ids`	text	NOT NULL
`data`	text	NOT NULL
`thread_id`	text	null

Indexes

UNIQUE (room_id, receipt_type, user_id) WHERE thread_id IS NULL receipts_graph_unique_index

Referenced by

nothing

receipts_linearized

9 cols · no RLS · line 635View in 3D

Enum-like column with no CHECK receipt_type — receipt_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — receipts_linearized references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`stream_id`	bigint	NOT NULL
`room_id`	text	NOT NULL
`receipt_type`	text	NOT NULL
`user_id`	text	NOT NULL
`event_id`	text	NOT NULL
`data`	text	NOT NULL
`instance_name`	text	null
`event_stream_ordering`	bigint	null
`thread_id`	text	null

Indexes

(stream_id) receipts_linearized_id
(room_id, stream_id) receipts_linearized_room_stream
UNIQUE (room_id, receipt_type, user_id) WHERE thread_id IS NULL receipts_linearized_unique_index
(user_id) receipts_linearized_user

Referenced by

nothing

presence

4 cols · no RLS · line 545View in 3D

Enum-like column with no CHECK state — state is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — presence references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id` UK	text	NOT NULL
`state`	varchar(20)	null
`status_msg`	text	null
`mtime`	bigint	null

Indexes

none

Referenced by

nothing

presence_stream

9 cols · no RLS · line 551View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Enum-like column with no CHECK state — state is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — presence_stream references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`stream_id`	bigint	null
`user_id`	text	null
`state`	text	null
`last_active_ts`	bigint	null
`last_federation_update_ts`	bigint	null
`last_user_sync_ts`	bigint	null
`status_msg`	text	null
`currently_active`	boolean	null
`instance_name`	text	null

Indexes

(stream_id, user_id) presence_stream_id
(state) WHERE state <> CAST('offline' AS text) presence_stream_state_not_offline_idx
(user_id) presence_stream_user_id

Referenced by

nothing

users_to_send_full_presence_to

2 cols · no RLS · line 965View in 3D

Column	Type	Null	Default	References	Notes
`user_id` PK	text	NOT NULL		users.name 1:1
`presence_stream_id`	bigint	null

Indexes

none

Referenced by

nothing

Media repository 5 tables

Locally uploaded files and cached remote ones, their generated thumbnails, and the URL preview cache.

Relationships

No foreign keys in this domain.

local_media_repository

10 cols · no RLS · line 496View in 3D

Enum-like column with no CHECK media_type — media_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — local_media_repository references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default
`media_id` UK	text	null
`media_type`	text	null
`media_length`	integer	null
`created_ts`	bigint	null
`upload_name`	text	null
`user_id`	text	null
`quarantined_by`	text	null
`url_cache`	text	null
`last_access_ts`	bigint	null
`safe_from_quarantine`	boolean	NOT NULL	FALSE

Indexes

(created_ts) WHERE url_cache IS NOT NULL local_media_repository_url_idx
(user_id, created_ts) users_have_local_media

Referenced by

nothing

local_media_repository_thumbnails

6 cols · no RLS · line 508View in 3D

Enum-like column with no CHECK thumbnail_type — thumbnail_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — local_media_repository_thumbnails references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`media_id`	text	null
`thumbnail_width`	integer	null
`thumbnail_height`	integer	null
`thumbnail_type`	text	null
`thumbnail_method`	text	null
`thumbnail_length`	integer	null

Indexes

UNIQUE (media_id, thumbnail_width, thumbnail_height, thumbnail_type, thumbnail_method) local_media_repository_thumbn_media_id_width_height_method_key
(media_id) local_media_repository_thumbnails_media_id

Referenced by

nothing

local_media_repository_url_cache

7 cols · no RLS · line 516View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — local_media_repository_url_cache references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`url`	text	null
`response_code`	integer	null
`etag`	text	null
`expires_ts`	bigint	null
`og`	text	null
`media_id`	text	null
`download_ts`	bigint	null

Indexes

(url, download_ts) local_media_repository_url_cache_by_url_download_ts
(expires_ts) local_media_repository_url_cache_expires_idx
(media_id) local_media_repository_url_cache_media_idx

Referenced by

nothing

remote_media_cache

9 cols · no RLS · line 687View in 3D

Enum-like column with no CHECK media_type — media_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — remote_media_cache references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`media_origin`	text	null
`media_id`	text	null
`media_type`	text	null
`created_ts`	bigint	null
`upload_name`	text	null
`media_length`	integer	null
`filesystem_id`	text	null
`last_access_ts`	bigint	null
`quarantined_by`	text	null

Indexes

none

Referenced by

nothing

remote_media_cache_thumbnails

8 cols · no RLS · line 698View in 3D

Enum-like column with no CHECK thumbnail_type — thumbnail_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — remote_media_cache_thumbnails references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`media_origin`	text	null
`media_id`	text	null
`thumbnail_width`	integer	null
`thumbnail_height`	integer	null
`thumbnail_method`	text	null
`thumbnail_type`	text	null
`thumbnail_length`	integer	null
`filesystem_id`	text	null

Indexes

UNIQUE (media_origin, media_id, thumbnail_width, thumbnail_height, thumbnail_type, thumbnail_method) remote_media_repository_thumbn_media_origin_id_width_height_met

Referenced by

nothing

User directory and statistics 13 tables

The searchable user directory, which users share rooms, and the rolled-up room and user statistics behind the admin views.

Relationships

No foreign keys in this domain.

user_directory

4 cols · no RLS · line 881View in 3D

Isolated table — user_directory references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`room_id`	text	null
`display_name`	text	null
`avatar_url`	text	null

Indexes

(room_id) user_directory_room_idx
UNIQUE (user_id) user_directory_user_idx

Referenced by

nothing

user_directory_search

2 cols · no RLS · line 887View in 3D

Isolated table — user_directory_search references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`user_id`	text	NOT NULL
`vector`	tsvector	null

Indexes

(vector) user_directory_search_fts_idx
UNIQUE (user_id) user_directory_search_user_idx

Referenced by

nothing

user_directory_stream_pos

2 cols · no RLS · line 891View in 3D

Isolated table — user_directory_stream_pos references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`lock` UK	char(1)	NOT NULL	CAST('X' AS bpchar)		`CHECK lock = CAST('X' AS bpchar)`
`stream_id`	bigint	null

Indexes

none

Referenced by

nothing

Table checks: lock = CAST('X' AS bpchar)

users_in_public_rooms

2 cols · no RLS · line 958View in 3D

Isolated table — users_in_public_rooms references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`user_id`	text	NOT NULL
`room_id`	text	NOT NULL

Indexes

(room_id) users_in_public_rooms_r_idx
UNIQUE (user_id, room_id) users_in_public_rooms_u_idx

Referenced by

nothing

users_who_share_private_rooms

3 cols · no RLS · line 969View in 3D

Isolated table — users_who_share_private_rooms references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`other_user_id`	text	NOT NULL
`room_id`	text	NOT NULL

Indexes

(other_user_id) users_who_share_private_rooms_o_idx
(room_id) users_who_share_private_rooms_r_idx
UNIQUE (user_id, other_user_id, room_id) users_who_share_private_rooms_u_idx

Referenced by

nothing

room_stats_current

9 cols · no RLS · line 745View in 3D

Isolated table — room_stats_current references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`room_id` PK	text	NOT NULL
`current_state_events`	integer	NOT NULL
`joined_members`	integer	NOT NULL
`invited_members`	integer	NOT NULL
`left_members`	integer	NOT NULL
`banned_members`	integer	NOT NULL
`local_users_in_room`	integer	NOT NULL
`completed_delta_stream_id`	bigint	NOT NULL
`knocked_members`	integer	null

Indexes

none

Referenced by

nothing

room_stats_state

11 cols · no RLS · line 760View in 3D

Enum-like column with no CHECK history_visibility — history_visibility is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Enum-like column with no CHECK room_type — room_type is a short string that clearly takes a fixed set of values, but the database accepts anything. Typos become new states, and nobody can list the legal values without reading application code.
Isolated table — room_stats_state references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`room_id`	text	NOT NULL
`name`	text	null
`canonical_alias`	text	null
`join_rules`	text	null
`history_visibility`	text	null
`encryption`	text	null
`avatar`	text	null
`guest_access`	text	null
`is_federatable`	boolean	null
`topic`	text	null
`room_type`	text	null

Indexes

UNIQUE (room_id) room_stats_state_room

Referenced by

nothing

room_stats_earliest_token

2 cols · no RLS · line 756View in 3D

Isolated table — room_stats_earliest_token references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`room_id`	text	NOT NULL
`token`	bigint	NOT NULL

Indexes

UNIQUE (room_id) room_stats_earliest_token_idx

Referenced by

nothing

user_stats_current

3 cols · no RLS · line 925View in 3D

Isolated table — user_stats_current references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id` PK	text	NOT NULL
`joined_rooms`	bigint	NOT NULL
`completed_delta_stream_id`	bigint	NOT NULL

Indexes

none

Referenced by

nothing

stats_incremental_position

2 cols · no RLS · line 821View in 3D

Isolated table — stats_incremental_position references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`lock` UK	char(1)	NOT NULL	CAST('X' AS bpchar)		`CHECK lock = CAST('X' AS bpchar)`
`stream_id`	bigint	NOT NULL

Indexes

none

Referenced by

nothing

Table checks: lock = CAST('X' AS bpchar)

user_daily_visits

4 cols · no RLS · line 875View in 3D

No primary key — Without a primary key rows are not individually addressable: no safe UPDATE/DELETE of one row, no logical replication, ORMs misbehave, and duplicates are legal.
Isolated table — user_daily_visits references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`device_id`	text	null
`timestamp`	bigint	NOT NULL
`user_agent`	text	null

Indexes

(timestamp) user_daily_visits_ts_idx
(user_id, timestamp) user_daily_visits_uts_idx

Referenced by

nothing

monthly_active_users

2 cols · no RLS · line 525View in 3D

Isolated table — monthly_active_users references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`user_id`	text	NOT NULL
`timestamp`	bigint	NOT NULL

Indexes

(timestamp) monthly_active_users_time_stamp
UNIQUE (user_id) monthly_active_users_users

Referenced by

nothing

user_ips

6 cols · no RLS · line 912View in 3D

Isolated table — user_ips references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`access_token`	text	NOT NULL
`device_id`	text	null
`ip`	text	NOT NULL
`user_agent`	text	NOT NULL
`last_seen`	bigint	NOT NULL

Indexes

(user_id, device_id, last_seen) user_ips_device_id
(user_id, last_seen) user_ips_last_seen
(last_seen) user_ips_last_seen_only
UNIQUE (user_id, access_token, ip) user_ips_user_token_ip_unique_index

Referenced by

nothing

Worker coordination 5 tables

How the processes that make up one homeserver stay in step: worker locks, the instance map, stream positions and cache invalidation, plus per-user rate-limit overrides.

Relationships

No foreign keys in this domain.

worker_locks

5 cols · no RLS · line 974View in 3D

Isolated table — worker_locks references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`lock_name`	text	NOT NULL
`lock_key`	text	NOT NULL
`instance_name`	text	NOT NULL
`token`	text	NOT NULL
`last_renewed_ts`	bigint	NOT NULL

Indexes

UNIQUE (lock_name, lock_key) worker_locks_key

Referenced by

nothing

instance_map

2 cols · no RLS · line 478View in 3D

Isolated table — instance_map references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null	Default	References	Notes
`instance_id` PK	integer	NOT NULL
`instance_name`	text	NOT NULL

Indexes

UNIQUE (instance_name) instance_map_idx

Referenced by

nothing

stream_positions

3 cols · no RLS · line 831View in 3D

Isolated table — stream_positions references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`stream_name`	text	NOT NULL
`instance_name`	text	NOT NULL
`stream_id`	bigint	NOT NULL

Indexes

UNIQUE (stream_name, instance_name) stream_positions_idx

Referenced by

nothing

cache_invalidation_stream_by_instance

5 cols · no RLS · line 85View in 3D

Isolated table — cache_invalidation_stream_by_instance references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`stream_id`	bigint	NOT NULL
`instance_name`	text	NOT NULL
`cache_func`	text	NOT NULL
`keys`	text[]	null
`invalidation_ts`	bigint	null

Indexes

UNIQUE (stream_id) cache_invalidation_stream_by_instance_id
(instance_name, stream_id) cache_invalidation_stream_by_instance_instance_index

Referenced by

nothing

ratelimit_override

3 cols · no RLS · line 622View in 3D

Isolated table — ratelimit_override references nothing and nothing references it. Either it is a staging/log table (fine, say so), or it is dead, or it is the seed of a second data model growing beside the first.

Column	Type	Null
`user_id`	text	NOT NULL
`messages_per_second`	bigint	null
`burst_count`	bigint	null

Indexes

UNIQUE (user_id) ratelimit_override_idx

Referenced by

nothing