pg_integrity_check — calculate and validate checksums for controlled files (certified edition only)
connection-option...] [ -s | --system ] [ -u | --user ] [ -c | --catalog ] [ -o | --output ] [ -D
datadir ] [ -v | --verbose ] [ -? | --help ]
pg_integrity_check is a utility provided with Postgres Pro Standard that can calculate and validate checksums for the objects you would like to control. When running
pg_integrity_check, you must specify at least one of the options that define the type of the controlled objects:
-c for read-only files, additional files, or system catalog tables, respectively.
If you use the
pg_integrity_check calculates checksums and writes them into configuration files under the
share/security/ directory. You must have write access to the corresponding files to perform this command. You cannot use the
-o option together with the
-s option, since a checksum for read-only files cannot be overwritten.
If you omit the
pg_integrity_check compares the calculated checksums with the corresponding checksums in the configuration files. If the checksums differ for any of the controlled objects,
pg_integrity_check displays a message indicating the difference.
For details on using
pg_integrity_check, see Section 31.2.
Standard options for connecting to a database:
-U. You must specify
-Uoptions when validating checksums for catalog tables with the
-coption. For detailed description of connection options, see psql.
Validate checksums for read-only files. Checksums for read-only files control both file contents and file attributes.
Validate checksums for additional files. Checksums for additional files control both file contents and file attributes.
Validate checksums for system catalog tables. For the
-coption to work correctly, you must also specify connection parameters for the database. The database server must be started and accept connections.
Recalculate checksums and write it into a file.
Data directory of the database cluster. This option is required to define the filenames for the generated configuration files when using
Print debugging information.
Print command-line help.
0 — checksums are calculated or validated successfully.
1 — an error occurred during the initial checksum calculation for read-only files.
2 — checksum validation revealed changes in one or more of the controlled objects.
3 — an unexpected error occurred during checksum validation.
Compute checksums for additional files and write them into the
share/security/_var_lib_pgpro_std-14_data.user.conf configuration file:
pg_integrity_check -u -o -D /var/lib/pgpro/std-14/data
Check integrity of all controlled objects in the
postgres database on behalf of the
pg_integrity_check -s -u -c -D /var/lib/pgpro/std-14/data -d postgres -h localhost -p 5432 -U postgres