← Graph

Multi-column indexes scoped by tenant

question 2 connections

Audience question: if everything is scoped by tenant and uniqueness is scoped by tenant, do all indexes need to be multi-column (tenant_id + …) rather than single-column? Speaker doesn't have a definitive answer but notes it intuitively helps, and flags Postgres table partitioning by tenant_id (partition pruning) as another long-term optimisation. Promises to follow up.

answer_summary
Intuitively yes for uniqueness/lookup patterns scoped by tenant, but speaker wants to verify. Physical partitioning by tenant_id is another long-term option.
question Multi-column indexes scoped by tenant
about
Performance follow-up to the row-level approach.
question Multi-column indexes scoped by tenant
asked_at
Asked in Q&A of the talk.

Provenance

Read by
1 extraction