diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 97aeadfc35f..afb8651f07b 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -7498,7 +7498,6 @@ local0.* /var/log/postgresql bgworker bgwriter checkpointer - checksums ioworker postmaster slotsyncworker @@ -12305,7 +12304,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - data_checksums (enum) + data_checksums (bool) data_checksums configuration parameter @@ -12313,8 +12312,6 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' Reports the state of data checksums for this cluster. - Possible values are on, off, - inprogress-on and inprogress-off. See for more information. diff --git a/doc/src/sgml/func/func-admin.sgml b/doc/src/sgml/func/func-admin.sgml index 408bf0214da..7deb28be9b0 100644 --- a/doc/src/sgml/func/func-admin.sgml +++ b/doc/src/sgml/func/func-admin.sgml @@ -3126,83 +3126,4 @@ SELECT convert_from(pg_read_binary_file('file_in_utf8.txt'), 'UTF8'); - - - Data Checksum Functions - - - The functions shown in can - be used to enable or disable data checksums in a running cluster. - - - Changing data checksums can be done in a cluster with concurrent activity - without blocking queries, but overall system performance will be affected. - See for further details on how changing the - data checksums state can affect a system and possible mitigations for how - to reduce the impact. - - - - Data Checksum Functions - - - - - Function - - - Description - - - - - - - - - pg_enable_data_checksums - - pg_enable_data_checksums ( cost_delay int, cost_limit int ) - void - - - Initiates the process of enabling data checksums for the cluster. This - will set the data checksums state to inprogress-on - as well as start a background worker that will process all pages in all - databases and enable data checksums on them. When all pages have - been processed, the cluster will automatically set data checksums state - to on. This operation is WAL logged and replicated - to all standby nodes. - - - If cost_delay and cost_limit are - specified, the process is throttled using the same principles as - Cost-based Vacuum Delay. - - - - - - - - pg_disable_data_checksums - - pg_disable_data_checksums () - void - - - Disables data checksum calculation and validation for the cluster. This - will set the data checksum state to inprogress-off - while data checksums are being disabled. When all active backends have - stopped validating data checksums, the data checksum state will be - set to off. - - - - - -
- - - diff --git a/doc/src/sgml/func/func-info.sgml b/doc/src/sgml/func/func-info.sgml index fc8d38872cd..230efca6dd6 100644 --- a/doc/src/sgml/func/func-info.sgml +++ b/doc/src/sgml/func/func-info.sgml @@ -3481,11 +3481,6 @@ acl | {postgres=arwdDxtm/postgres,foo=r/postgres} xid - - data_page_checksum_version - integer - - checkpoint_time timestamp with time zone diff --git a/doc/src/sgml/glossary.sgml b/doc/src/sgml/glossary.sgml index cbcd1440c69..d8a304d5583 100644 --- a/doc/src/sgml/glossary.sgml +++ b/doc/src/sgml/glossary.sgml @@ -234,9 +234,8 @@ which runs system- or user-supplied code. Serves as infrastructure for several features in PostgreSQL, such as - logical replication, - parallel queries and - data checksums processing. + logical replication and + parallel queries. In addition, Extensions can add custom background worker processes. @@ -575,21 +574,6 @@ - - Data Checksums (process) - - - A set of - background worker - processes which can enable or disable data checksums in a running cluster. - The process which coordinates the work is known as the - data checksums launcher and the process which - operates on the individual databases is known as the - data checksums worker. - - - - Database diff --git a/doc/src/sgml/images/Makefile b/doc/src/sgml/images/Makefile index e805487344d..fd55b9ad23f 100644 --- a/doc/src/sgml/images/Makefile +++ b/doc/src/sgml/images/Makefile @@ -3,7 +3,6 @@ # see README in this directory about image handling ALL_IMAGES = \ - datachecksums.svg \ genetic-algorithm.svg \ gin.svg \ pagelayout.svg \ diff --git a/doc/src/sgml/images/datachecksums.gv b/doc/src/sgml/images/datachecksums.gv deleted file mode 100644 index dff3ff7340a..00000000000 --- a/doc/src/sgml/images/datachecksums.gv +++ /dev/null @@ -1,14 +0,0 @@ -digraph G { - A -> B [label="SELECT pg_enable_data_checksums()"]; - B -> C; - D -> A; - C -> D [label="SELECT pg_disable_data_checksums()"]; - E -> A [label=" --no-data-checksums"]; - E -> C [label=" --data-checksums"]; - - A [label="off"]; - B [label="inprogress-on"]; - C [label="on"]; - D [label="inprogress-off"]; - E [label="initdb"]; -} diff --git a/doc/src/sgml/images/datachecksums.svg b/doc/src/sgml/images/datachecksums.svg deleted file mode 100644 index 8c58f42922e..00000000000 --- a/doc/src/sgml/images/datachecksums.svg +++ /dev/null @@ -1,81 +0,0 @@ - - - - - -G - - - -A - -off - - - -B - -inprogress-on - - - -A->B - - -SELECT pg_enable_data_checksums() - - - -C - -on - - - -B->C - - - - - -D - -inprogress-off - - - -C->D - - -SELECT pg_disable_data_checksums() - - - -D->A - - - - - -E - -initdb - - - -E->A - - - --no-data-checksums - - - -E->C - - - --data-checksums - - - diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 93968294e5d..86982079362 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -436,15 +436,6 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser - - pg_stat_progress_data_checksumspg_stat_progress_data_checksums - One row for the data checksum launcher process while data - checksums are being enabled or disabled. When enabling data - checksums, the view also has one row for each worker process, - showing current progress. - See . - - @@ -6136,10 +6127,10 @@ FROM pg_stat_get_backend_idset() AS backendid; which support progress reporting are ANALYZE, COPY, CREATE INDEX, REPACK (and its obsolete spelling CLUSTER), - VACUUM, + VACUUM and (i.e., replication command that issues to take - a base backup), and online data checksum operations. + a base backup). This may be expanded in the future. @@ -7867,221 +7858,6 @@ FROM pg_stat_get_backend_idset() AS backendid; - - - Data Checksum Progress Reporting - - - pg_stat_progress_data_checksums - - - - When data checksums are being enabled or disabled on a running cluster, the - pg_stat_progress_data_checksums view will contain - a row for the launcher process. When enabling data checksums, the view - will also contain one row for each worker process which is currently - calculating and writing checksums for the data pages in a database. The - launcher provides an overview of the overall progress, such as how many - databases have been processed and how many remain, while the workers track - progress for currently processed databases. - - - - <structname>pg_stat_progress_data_checksums</structname> View - - - - - - Column Type - - - Description - - - - - - - - - - pid integer - - - Process ID of the data checksum process, launcher or worker. - - - - - - - - datid oid - - - OID of this database, or 0 for the launcher process. - - - - - - - - datname name - - - Name of this database, or NULL for the - launcher process. - - - - - - - - phase text - - - Current processing phase, see - for description of the phases. - - - - - - - - databases_total bigint - - - The total number of databases which will be processed. Only the - launcher process has this value set when enabling data checksums; - otherwise this is set to NULL. - - - - - - - - databases_done bigint - - - The number of databases which have been processed. Only the launcher - process has this value set when enabling data checksums; otherwise - this is set to NULL. - - - - - - - - relations_total bigint - - - The total number of relations which will be processed, or - NULL if the worker process hasn't - calculated the number of relations yet. The launcher process has - this set to NULL since it isn't responsible for - processing relations, only launching worker processes. - - - - - - - - relations_done bigint - - - The number of relations which have been processed. The launcher - process has this set to NULL. - - - - - - - - blocks_total bigint - - - The number of blocks in the current relation which will be processed, - or NULL if the worker process hasn't - calculated the number of blocks yet. The launcher process has - this set to NULL. - - - - - - - - blocks_done bigint - - - The number of blocks in the current relation which have been processed. - The launcher process has this set to NULL. - - - - - - -
- - - Data Checksum Phases - - - - - - Phase - Description - - - - - enabling - - The command is currently enabling data checksums on the cluster. - - - - disabling - - The command is currently disabling data checksums on the cluster. - - - - done - - The command is done and the data checksum state in the cluster has - changed. - - - - waiting on barrier - - The command is currently waiting for the current active backends to - acknowledge the change in data checksum state. - - - - waiting on temporary tables - - The command is currently waiting for all temporary tables which existed - at the time the command was started to be removed. - - - - -
- - diff --git a/doc/src/sgml/ref/pg_basebackup.sgml b/doc/src/sgml/ref/pg_basebackup.sgml index 3117968d125..fecee08b0a5 100644 --- a/doc/src/sgml/ref/pg_basebackup.sgml +++ b/doc/src/sgml/ref/pg_basebackup.sgml @@ -788,12 +788,6 @@ PostgreSQL documentation in the pg_stat_database view. - - Checksums must be enabled on the server for the duration of the base - backup in order to be verified. If checksums are in the process of - being enabled when the base backup starts then checksum verification is - disabled for the base backup. - diff --git a/doc/src/sgml/ref/pg_checksums.sgml b/doc/src/sgml/ref/pg_checksums.sgml index ae66fad3f0f..fcded6b4a05 100644 --- a/doc/src/sgml/ref/pg_checksums.sgml +++ b/doc/src/sgml/ref/pg_checksums.sgml @@ -39,23 +39,13 @@ PostgreSQL documentation pg_checksums checks, enables or disables data checksums in a PostgreSQL cluster. The server must be shut down cleanly before running pg_checksums. - Checksums can also be enabled while the cluster is running using - processing, see - for further details on the different approaches. + See for further details on data checksums. When verifying checksums, the exit status is zero if there are no checksum errors, and nonzero if at least one checksum failure is detected. When enabling or disabling checksums, the exit status is nonzero if the operation failed. - - When enabling checksums with pg_checksums, if - checksums were in the process of being enabled using - when the cluster was shut - down, pg_checksums will still process all - relation files regardless of the progress of online checksum processing. - - When verifying checksums, every file in the cluster is scanned. When enabling checksums, each relation file block with a changed checksum is diff --git a/doc/src/sgml/regress.sgml b/doc/src/sgml/regress.sgml index c74941bfbf2..873387ec168 100644 --- a/doc/src/sgml/regress.sgml +++ b/doc/src/sgml/regress.sgml @@ -275,20 +275,6 @@ make check-world PG_TEST_EXTRA='kerberos ldap ssl load_balance libpq_encryption' The following values are currently supported: - - checksum, checksum_extended - - - Runs additional tests for enabling data checksums which inject faults - to cause re-tries in the processing, as well as tests that run pgbench - concurrently and randomly restarts the cluster. Some of these test - suites require injection points enabled in the installation. - checksum_extended is an extended version with - longer runtime, injected random delays and larger datasets. - - - - kerberos diff --git a/doc/src/sgml/release-19.sgml b/doc/src/sgml/release-19.sgml index 4577d06ac2b..0266d6a98e0 100644 --- a/doc/src/sgml/release-19.sgml +++ b/doc/src/sgml/release-19.sgml @@ -47,13 +47,6 @@ - - - Data checksums can now be - enabled or disabled while the database server is running. - - - A new WAIT @@ -1353,34 +1346,6 @@ The previous warning was 40 million. Warnings are issued to clients and in the Server Configuration - - - - -Allow online enabling and disabling of data checksums (Daniel Gustafsson, Magnus Hagander, Tomas Vondra) -§ -§ -§ - - - -Previously the checksum status could only be changed while the cluster was offline using pg_checksums. - - - -Application pg_controldata and function pg_control_checkpoint() report -the checksum status at the time of the most recent checkpoint, and function pg_control_init() reports -checksum status at the time the cluster was initialized. - -