2016-02-26 01:08:32 +01:00
|
|
|
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".
|
|
|
|
|
|
Add an enforcement mechanism for global object names in regression tests.
In commit 18555b132 we tentatively established a rule that regression
tests should use names containing "regression" for databases, and names
starting with "regress_" for all other globally-visible object names, so
as to circumscribe the side-effects that "make installcheck" could have
on an existing installation.
This commit adds a simple enforcement mechanism for that rule: if the code
is compiled with ENFORCE_REGRESSION_TEST_NAME_RESTRICTIONS defined, it
will emit a warning (not an error) whenever a database, role, tablespace,
subscription, or replication origin name is created that doesn't obey the
rule. Running one or more buildfarm members with that symbol defined
should be enough to catch new violations, at least in the regular
regression tests. Most TAP tests wouldn't notice such warnings, but
that's actually fine because TAP tests don't execute against an existing
server anyway.
Since it's already the case that running src/test/modules/ tests in
installcheck mode is deprecated, we can use that as a home for tests
that seem unsafe to run against an existing server, such as tests that
might have side-effects on existing roles. Document that (though this
commit doesn't in itself make it any less safe than before).
Update regress.sgml to define these restrictions more clearly, and
to clean up assorted lack-of-up-to-date-ness in its descriptions of
the available regression tests.
Discussion: https://postgr.es/m/16638.1468620817@sss.pgh.pa.us
2019-06-29 17:34:00 +02:00
|
|
|
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.
|
|
|
|
|
|
2016-02-26 01:08:32 +01:00
|
|
|
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.
|
