mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-09-28 16:11:48 +02:00
72a5b1fc88
@extschema:name@ extends the existing @extschema@ feature so that we can also insert the schema name of some required extension, thus making cross-extension references robust even if they are in different schemas. However, this has the same hazard as @extschema@: if the schema name is embedded literally in an installed object, rather than being looked up once during extension script execution, then it's no longer safe to relocate the other extension to another schema. To deal with that without restricting things unnecessarily, add a "no_relocate" option to extension control files. This allows an extension to specify that it cannot handle relocation of some of its required extensions, even if in themselves those extensions are relocatable. We detect "no_relocate" requests of dependent extensions during ALTER EXTENSION SET SCHEMA. Regina Obe, reviewed by Sandro Santilli and myself Discussion: https://postgr.es/m/003001d8f4ae$402282c0$c0678840$@pcorp.us |
||
---|---|---|
.. | ||
brin | ||
commit_ts | ||
delay_execution | ||
dummy_index_am | ||
dummy_seclabel | ||
ldap_password_func | ||
libpq_pipeline | ||
plsample | ||
snapshot_too_old | ||
spgist_name_ops | ||
ssl_passphrase_callback | ||
test_bloomfilter | ||
test_copy_callbacks | ||
test_custom_rmgrs | ||
test_ddl_deparse | ||
test_extensions | ||
test_ginpostinglist | ||
test_integerset | ||
test_lfind | ||
test_misc | ||
test_oat_hooks | ||
test_parser | ||
test_pg_db_role_setting | ||
test_pg_dump | ||
test_predtest | ||
test_rbtree | ||
test_regex | ||
test_rls_hooks | ||
test_shm_mq | ||
test_slru | ||
unsafe_tests | ||
worker_spi | ||
Makefile | ||
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.