Optimize recurring bookings indexes with separate recurring/regular booking indexes

Author: naqvis

migration/db/migrations/20251211120000000_optimize_bookings_query_indexes.sql

@@ -18,9 +18,14 @@ CREATE INDEX IF NOT EXISTS bookings_zones_gin_idx
   WHERE deleted = FALSE AND checked_out_at IS NULL;
 
 -- Create a composite index for recurring bookings queries
-CREATE INDEX IF NOT EXISTS bookings_recurring_lookup_idx
-  ON bookings USING BTREE (tenant_id, recurrence_type, recurrence_end, booking_start)
-  WHERE deleted = FALSE AND rejected_at IS NULL AND deleted_at IS NULL;
+CREATE INDEX CONCURRENTLY IF NOT EXISTS bookings_recurring_idx
+  ON bookings (tenant_id, booking_start, recurrence_end)
+  WHERE recurrence_type <> 'NONE';
+
+-- Create a composite index for regular (non-recurring) bookings time range queries
+CREATE INDEX CONCURRENTLY IF NOT EXISTS bookings_regular_time_idx
+  ON bookings (tenant_id, booking_start, booking_end)
+  WHERE recurrence_type = 'NONE';
 
 -- Create a partial index for active bookings (not checked out, not deleted)
 CREATE INDEX IF NOT EXISTS bookings_active_idx
@@ -38,7 +43,8 @@ CREATE INDEX IF NOT EXISTS bookings_tenant_type_time_zones_idx
 
 DROP INDEX IF EXISTS bookings_tenant_type_time_zones_idx;
 DROP INDEX IF EXISTS bookings_active_idx;
-DROP INDEX IF EXISTS bookings_recurring_lookup_idx;
+DROP INDEX IF EXISTS bookings_regular_time_idx;
+DROP INDEX IF EXISTS bookings_recurring_idx;
 DROP INDEX IF EXISTS bookings_zones_gin_idx;
 DROP INDEX IF EXISTS bookings_tenant_type_deleted_time_idx;
 DROP INDEX IF EXISTS bookings_tenant_id_btree_idx;