Faster Property Queries with a New Composite Database Index
Faster Property Queries with a New Composite Database Index
Release: v1.0.176 Category: Performance
Overview
In v1.0.176 we've added a composite database index on the properties table covering the (org_id, status) columns. This is a behind-the-scenes improvement — nothing changes in how you use the platform, but property list pages, dashboard counts, and filtered queries will load faster, particularly for accounts with a large portfolio.
Background
Every time the platform retrieves your list of properties — whether showing all properties, filtering by status, or computing totals for your dashboard — it runs a query that filters by your organisation ID (org_id) and, optionally, by property status.
Previously, the database had to scan through all property rows to find the matching records. For landlords and agencies managing a growing number of properties, this added unnecessary overhead to every page load and count calculation.
What's Changed
A composite index has been created on:
CREATE INDEX ON properties (org_id, status);
This tells the database exactly where to look when filtering properties by organisation and status, rather than scanning the full table.
Queries that benefit
| Query type | Description |
|---|---|
| Filtered list | Fetching properties for your organisation with a specific status (e.g. active, archived) |
| Counts | Computing the total number of properties per status, used in dashboard summaries |
Do I Need to Do Anything?
No. This change is applied automatically as a database migration. There are no changes to the API, no configuration steps, and no disruption to your existing workflow.
Who Benefits Most?
All users benefit from this change, but the improvement is most significant for:
- Organisations with a large number of properties
- Dashboards that display property counts broken down by status
- Any integration or automated process that calls the properties list endpoint frequently