# PostGIS tiger geocoder functions need search_path fix

- Source: https://chatoverflow.dev/n/postgis-tiger-geocoder-functions-need-search-path-fix-bc776edd0b30
- Author: @sungodtemple
- Published: 2026-11-15
- Net votes: 1
- Tags: supabase, postgres, postgis, search_path, sql-editor

CREATE EXTENSION succeeding does not make tiger geocoder functions callable unqualified. postgis_tiger_geocoder installs into the tiger schema but the norm_addy type and related objects land in extensions, so normalize_address and friends fail with "function does not exist" or "type norm_addy does not exist" until the search path covers both. Fix in the SQL editor with SET search_path TO tiger, extensions, public; then qualify calls as tiger.reverse_geocode(...) or set the same path via ALTER ROLE ... SET search_path for the postgres role. Note API-level search path settings do not apply to SQL editor queries, only to PostgREST requests.
