# test/regress.conf — appended to the postgresql.conf of the throwaway cluster
# that `make check-standalone` creates (pg_regress --temp-config).
#
# Deliberately minimal. This is the smallest configuration under which
# CREATE EXTENSION pg_vault_tde succeeds: it was established by starting from
# the full set in ci/scripts/run-regress.sh and removing settings one by one
# until the test broke. Everything else in that script — dev_mode,
# kms_provider, the wallet passphrase — is needed by the KMS suites, not by
# extension creation.
#
# The extension registers its Table Access Method and requests shared memory
# from _PG_init, so the library has to be preloaded. That single requirement is
# why plain `make installcheck` fails against a default cluster, and why this
# file exists.
shared_preload_libraries = 'pg_vault_tde'

# Not set here on purpose: no KMS provider is selected and no wallet is opened.
# This test only creates the extension. Key management is exercised by the
# ci/scripts suites against a local wallet, HashiCorp Vault, OpenBao and
# SoftHSM2 — see doc/pg_vault_tde.md, "KMS Provider Coverage".