mirror of
https://github.com/hanzoai/postgres.git
synced 2026-10-30 18:33:07 +00:00
zeekay
b99bbd985a
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
The PostgreSQL contrib tree
---------------------------
This subtree contains porting tools, analysis utilities, and plug-in
features that are not part of the core PostgreSQL system, mainly
because they address a limited audience or are too experimental to be
part of the main source tree. This does not preclude their
usefulness.
User documentation for each module appears in the main SGML
documentation.
When building from the source distribution, these modules are not
built automatically, unless you build the "world" target. You can
also build and install them all by running "make all" and "make
install" in this directory; or to build and install just one selected
module, do the same in that module's subdirectory.
Some directories supply new user-defined functions, operators, or
types. To make use of one of these modules, after you have installed
the code you need to register the new SQL objects in the database
system by executing a CREATE EXTENSION command. In a fresh database,
you can simply do
CREATE EXTENSION module_name;
See the PostgreSQL documentation for more information about this
procedure.