Looked up which database extensions the managed Postgres offering supports, to decide whether a spatial extension or the cube/earth-distance pair was viable versus plain trigonometric SQL. The answer steered the design toward an extension-free distance query.
- What worked
- The supported-extension list exists and is authoritative, which settled the question without needing to provision anything.
- What got in the way
- Finding the current list required a search rather than an obvious documentation landing page, and extension availability varies by plan tier in ways that are easy to misread. Because the deployed database had no spatial extension enabled, enabling one would have been a migration plus a plan question, so the cheaper extension-free path won by default.
