postgresql/src/bin/pg_amcheck
Tom Lane 32a85ee46b Don't fail on libpq-generated error reports in pg_amcheck.
An error PGresult generated by libpq itself, such as a report of
connection loss, won't have broken-down error fields.
should_processing_continue() blithely assumed that
PG_DIAG_SEVERITY_NONLOCALIZED would always be present, and would
dump core if it wasn't.

Per grepping to see if 6d157e7cb's mistake was repeated elsewhere.
2022-06-06 11:26:57 -04:00
..
po Translation updates 2022-05-09 12:26:57 +02:00
t Allow db.schema.table patterns, but complain about random garbage. 2022-04-20 11:39:44 -04:00
.gitignore Add pg_amcheck, a CLI for contrib/amcheck. 2021-03-12 13:00:01 -05:00
Makefile Add pg_amcheck, a CLI for contrib/amcheck. 2021-03-12 13:00:01 -05:00
nls.mk Translation updates 2021-11-08 10:06:30 +01:00
pg_amcheck.c Don't fail on libpq-generated error reports in pg_amcheck. 2022-06-06 11:26:57 -04:00
README Doc: add note about how to run the pg_amcheck regression tests. 2021-03-13 11:10:30 -05:00

src/bin/pg_amcheck/README

pg_amcheck is a command-line tool for running the amcheck extension.

Running the regression tests
============================

NOTE: You must have given the --enable-tap-tests argument to configure.
Also, to use "make installcheck", you must have built and installed
contrib/amcheck and contrib/pageinspect in addition to the core code.

Run
    make check
or
    make installcheck
You can use "make installcheck" if you previously did "make install".
In that case, the code in the installation tree is tested.  With
"make check", a temporary installation tree is built from the current
sources and then tested.