Editing Corpus/Schema (section)

== Benchmark results ==

Measured on 3.4M rows, PostgreSQL 16, single-node, 16 GB RAM.

{| class="wikitable"
! Query !! Corpus schema !! Previous 16-table schema !! Speedup
|-
| Tag filter + date range || 0.9 ms || — || B-tree scan, instant
|-
| FTS + tag filter (broad, 111K results) || 4.4 s || 31 s || 7x faster (BitmapAnd vs Seq Scan)
|-
| Tag-only + date || 1.4 ms || — || B-tree scan, instant
|-
| FTS narrow (17K results, warm) || 565 ms || — || Partial GIN index
|-
| Get by ID || 0.3 ms || 0.3 ms || PK lookup
|-
| Tag discovery (GROUP BY court, 3.4M rows) || 2.7 s || — || Seq scan — justifies tag_stats
|}

The FTS speedup comes from BitmapAnd of GIN (FTS) + GIN (tags) indexes. The previous schema used a Parallel Seq Scan because the planner could not combine B-tree (court column) with GIN (FTS) efficiently.

----