upstream/postgresql
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2026-02-27 11:50:33 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
postgresql/src/test/modules
History
Tom Lane 121e3ceed6 Avoid using INFO elevel for what are fundamentally debug messages. 
Commit 6f6b99d13 stuck an INFO message into the fast path for
checking partition constraints, for no very good reason except
that it made it easy for the regression tests to verify that
that path was taken.  Assorted later patches did likewise,
increasing the unsuppressable-chatter level from ALTER TABLE
even more.  This isn't good for the user experience, so let's
drop these messages down to DEBUG1 where they belong.  So as
not to have a loss of test coverage, create a TAP test that
runs the relevant queries with client_min_messages = DEBUG1
and greps for the expected messages.

This testing method is a bit brute-force --- in particular,
it duplicates the execution of a fair amount of the core
create_table and alter_table tests.  We experimented with
other solutions, but running any significant amount of
standard testing with client_min_messages = DEBUG1 seems
to have a lot of output-stability pitfalls, cf commits
bbb96c370 and 5655565c0.  Possibly at some point we'll look
into whether we can reduce the amount of test duplication.

Backpatch into v12, because some of these messages are new
in v12 and we don't really want to ship it that way.

Sergei Kornilov

Discussion: https://postgr.es/m/81911511895540@web58j.yandex.ru
Discussion: https://postgr.es/m/4859321552643736@myt5-02b80404fd9e.qloud-c.yandex.net
2019-09-07 19:03:11 -04:00
..
brin Add PGXS options to control TAP and isolation tests, take two 2018-12-03 09:27:35 +09:00
commit_ts Initial pgperltidy run for v12. 2019-05-22 13:36:19 -04:00
dummy_seclabel Update copyright for 2019 2019-01-02 12:44:25 -05:00
snapshot_too_old Add PGXS options to control TAP and isolation tests, take two 2018-12-03 09:27:35 +09:00
test_bloomfilter Update copyright for 2019 2019-01-02 12:44:25 -05:00
test_ddl_deparse Avoid order-of-execution problems with ALTER TABLE ADD PRIMARY KEY. 2019-04-23 12:25:27 -04:00
test_extensions Simplify restriction handling of two-phase commit for temporary objects 2019-01-26 10:45:23 +09:00
test_integerset Fix more typos and inconsistencies in the tree 2019-06-17 16:13:16 +09:00
test_misc Avoid using INFO elevel for what are fundamentally debug messages. 2019-09-07 19:03:11 -04:00
test_parser Update copyright for 2019 2019-01-02 12:44:25 -05:00
test_pg_dump Add PGXS options to control TAP and isolation tests, take two 2018-12-03 09:27:35 +09:00
test_predtest Teach optimizer's predtest.c more things about ScalarArrayOpExpr. 2019-03-01 17:14:17 -05:00
test_rbtree Update copyright for 2019 2019-01-02 12:44:25 -05:00
test_rls_hooks Fix more strcmp() calls using boolean-like comparisons for result checks 2019-04-12 10:16:49 +09:00
test_shm_mq Phase 2 pgindent run for v12. 2019-05-22 13:04:48 -04:00
unsafe_tests Move rolenames test out of the core regression tests. 2019-06-30 12:51:12 -04:00
worker_spi worker_spi needs a .gitignore file now. 2019-06-02 11:13:23 -04:00
Makefile Avoid using INFO elevel for what are fundamentally debug messages. 2019-09-07 19:03:11 -04:00
README Add an enforcement mechanism for global object names in regression tests. 2019-06-29 11:34:00 -04:00

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.