Various test suites use the "openssl" program as part of their setup. There isn't a way to override which openssl program is to be used, other than by fiddling with the path, perhaps. This has gotten increasingly problematic because different versions of openssl have different capabilities and do different things by default. This patch checks for an openssl binary in configure and meson setup, with appropriate ways to override it. This is similar to how "lz4" and "zstd" are handled, for example. The meson build system actually already did this, but the result was only used in some places. This is now applied more uniformly. Reviewed-by: Michael Paquier <michael@paquier.xyz> Discussion: https://www.postgresql.org/message-id/flat/dc638b75-a16a-007d-9e1c-d16ed6cf0ad2%40enterprisedb.com |
||
---|---|---|
.. | ||
brin | ||
commit_ts | ||
delay_execution | ||
dummy_index_am | ||
dummy_seclabel | ||
libpq_pipeline | ||
plsample | ||
snapshot_too_old | ||
spgist_name_ops | ||
ssl_passphrase_callback | ||
test_bloomfilter | ||
test_copy_callbacks | ||
test_ddl_deparse | ||
test_extensions | ||
test_ginpostinglist | ||
test_integerset | ||
test_lfind | ||
test_misc | ||
test_oat_hooks | ||
test_parser | ||
test_pg_dump | ||
test_predtest | ||
test_rbtree | ||
test_regex | ||
test_rls_hooks | ||
test_shm_mq | ||
unsafe_tests | ||
worker_spi | ||
Makefile | ||
README | ||
meson.build |
README
Test extensions and libraries ============================= src/test/modules contains PostgreSQL extensions that are primarily or entirely intended for testing PostgreSQL and/or to serve as example code. The extensions here aren't intended to be installed in a production server and aren't suitable for "real work". Furthermore, while you can do "make install" and "make installcheck" in this directory or its children, it is NOT ADVISABLE to do so with a server containing valuable data. Some of these tests may have undesirable side-effects on roles or other global objects within the tested server. "make installcheck-world" at the top level does not recurse into this directory. Most extensions have their own pg_regress tests or isolationtester specs. Some are also used by tests elsewhere in the tree. If you're adding new hooks or other functionality exposed as C-level API this is where to add the tests for it.