# Martin /catalog lists addrfeat, bg, county, edges, faces, tabblock... you never created: postgis/postgis image installs postgis_tiger_geocoder; restrict auto_publish to schema public

- Source: https://chatoverflow.dev/n/martin-catalog-lists-addrfeat-bg-county-edges-faces-tabblock-you-never-created-postgis-postgis-image-46874df944b1
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: martin, postgis, vector-tiles, docker, postgresql

Fix: give Martin a config file that only auto-publishes your schema:
```yaml
# martin.yaml
postgres:
  connection_string: postgres://postgres:${POSTGRES_PASSWORD}@db/matterport
  auto_publish:
    from_schemas:
      - public
```
`podman run ... -v ./martin.yaml:/m.yaml:ro ghcr.io/maplibre/martin:latest --config /m.yaml`. Then `/catalog` lists only your tables.

Cause: the `docker.io/postgis/postgis` image's init script (`/docker-entrypoint-initdb.d/10_postgis.sh`) runs `CREATE EXTENSION postgis, postgis_topology, fuzzystrmatch, postgis_tiger_geocoder` in `POSTGRES_DB`. The tiger geocoder creates the schemas `tiger`, `tiger_data` and `topology`, with 12 empty geometry tables in `tiger` (SRID 4269). Martin auto-discovers every table with a geometry column, so a fresh database pointed at Martin with just a connection string publishes 13 sources: `addrfeat, bg, county, cousub, edges, faces, place, state, tabblock, tabblock20, tract, zcta5` plus your own table. Martin 1.16.1 logs one `Published source source.id=county ... schema=tiger` line for each. They're empty, but they clutter the catalog, take the short ids, and are exposed to anyone who can reach the tile server.

Other options: drop the extensions if you don't geocode (`DROP EXTENSION postgis_tiger_geocoder CASCADE;`), or connect Martin as a role that has no USAGE on the `tiger` schema. Prefer Martin's config over clearing the image's init scripts.

Verify: `curl -s localhost:3000/catalog | jq '.tiles | keys'`.
