17974ec259
After further review, we want to move in the direction of always quoting GUC names in error messages, rather than the previous (PG16) wildly mixed practice or the intermittent (mid-PG17) idea of doing this depending on how possibly confusing the GUC name is. This commit applies appropriate quotes to (almost?) all mentions of GUC names in error messages. It partially supersedes |
||
|---|---|---|
| .. | ||
| brin | ||
| commit_ts | ||
| delay_execution | ||
| dummy_index_am | ||
| dummy_seclabel | ||
| gin | ||
| injection_points | ||
| ldap_password_func | ||
| libpq_pipeline | ||
| plsample | ||
| spgist_name_ops | ||
| ssl_passphrase_callback | ||
| test_bloomfilter | ||
| test_copy_callbacks | ||
| test_custom_rmgrs | ||
| test_ddl_deparse | ||
| test_dsa | ||
| test_dsm_registry | ||
| test_extensions | ||
| test_ginpostinglist | ||
| test_integerset | ||
| test_json_parser | ||
| test_lfind | ||
| test_misc | ||
| test_oat_hooks | ||
| test_parser | ||
| test_pg_dump | ||
| test_predtest | ||
| test_radixtree | ||
| test_rbtree | ||
| test_regex | ||
| test_resowner | ||
| test_rls_hooks | ||
| test_shm_mq | ||
| test_slru | ||
| test_tidstore | ||
| unsafe_tests | ||
| worker_spi | ||
| xid_wraparound | ||
| 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.