zeekay b99bbd985a fix: make ZAP opt-in so hanzo/sql works as vanilla PostgreSQL ...

The zap_fdw background worker previously always registered itself and
connected to a hardcoded "postgres" database. This broke deployments
that don't use ZAP or use a different database name.

Changes:
- Add zap.enabled GUC (default false) — worker only starts when true
- Add zap.database GUC — falls back to POSTGRES_DB env var then "postgres"
- Build zap_fdw in Dockerfile but keep it out of shared_preload_libraries
- Fix compile errors: move got_sigterm before use, add signal handler
- Fix Makefile PG_MAJOR (16 -> 18), compose.yml (use hanzo/sql:18)
- Remove hardcoded database names from healthchecks and init.sql
- Trigger CI on contrib/zap_fdw/** changes

2026-03-30 19:15:44 -07:00

..

postgresql.conf

fix: make ZAP opt-in so hanzo/sql works as vanilla PostgreSQL

2026-03-30 19:15:44 -07:00