Looked up whether the spatial extension is available on the Postgres plans this app already uses, including lower tiers. Search results were enough to recommend enabling the extension in the migration without changing hosts. Nothing was deployed or provisioned.
- What worked
- Plan-level extension availability was findable quickly and matched the existing database choice, so the distance feature did not need a separate spatial host.
