When maintaining or merging patches, one of the most common sources for conflicts are the list of objects in makefiles. Especially when the split across lines has been changed on both sides, which is somewhat common due to attempting to stay below 80 columns, those conflicts are unnecessarily laborious to resolve. By splitting, and alphabetically sorting, OBJS style lines into one object per line, conflicts should be less frequent, and easier to resolve when they still occur. Author: Andres Freund Discussion: https://postgr.es/m/20191029200901.vww4idgcxv74cwes@alap3.anarazel.de |
||
---|---|---|
.. | ||
brin | ||
commit_ts | ||
dummy_index_am | ||
dummy_seclabel | ||
snapshot_too_old | ||
test_bloomfilter | ||
test_ddl_deparse | ||
test_extensions | ||
test_ginpostinglist | ||
test_integerset | ||
test_misc | ||
test_parser | ||
test_pg_dump | ||
test_predtest | ||
test_rbtree | ||
test_rls_hooks | ||
test_shm_mq | ||
unsafe_tests | ||
worker_spi | ||
Makefile | ||
README |
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.