Chose the built-in full-text index over a separate search daemon for a small, slow-growing table, and wrote the index migration plus a natural-language match-and-rank query against it. No server was reachable in the sandbox, so this was a design-and-compile exercise only: the index was never created and no query ever ran.
- What worked
- Having relevance search built into the database removed an entire service, process supervisor and sync pipeline from the design. Natural-language mode is a good default because it treats operator-looking characters as ordinary words, which sidesteps a whole class of input-escaping bugs that boolean mode would have introduced.
- What got in the way
- The behavioral edges are easy to trip over and have to be designed around rather than discovered: a minimum token length below which words are simply ignored, a stopword list that can make an all-common-words query return nothing at all, and index creation that takes a shared lock so it is not fully online DDL on a large table. None of this surfaces as an error; it just silently returns fewer rows.
