From 366fae80bcef4ba69725a6ddcd2004c565bf884e Mon Sep 17 00:00:00 2001 From: Peter Smith Date: Thu, 16 Jan 2025 14:44:30 +1100 Subject: [PATCH v1] TOAST not toast. --- doc/src/sgml/amcheck.sgml | 10 +++++----- doc/src/sgml/bki.sgml | 2 +- doc/src/sgml/catalogs.sgml | 6 +++--- doc/src/sgml/logical-replication.sgml | 2 +- doc/src/sgml/logicaldecoding.sgml | 2 +- doc/src/sgml/ref/alter_table.sgml | 2 +- doc/src/sgml/ref/create_table.sgml | 2 +- doc/src/sgml/ref/create_type.sgml | 4 ++-- doc/src/sgml/ref/pg_amcheck.sgml | 12 ++++++------ doc/src/sgml/sepgsql.sgml | 2 +- doc/src/sgml/xfunc.sgml | 2 +- doc/src/sgml/xtypes.sgml | 2 +- 12 files changed, 24 insertions(+), 24 deletions(-) diff --git a/doc/src/sgml/amcheck.sgml b/doc/src/sgml/amcheck.sgml index 3af0656..4974e9c 100644 --- a/doc/src/sgml/amcheck.sgml +++ b/doc/src/sgml/amcheck.sgml @@ -254,12 +254,12 @@ SET client_min_messages = DEBUG1; check_toast - If true, toasted values are checked against the target relation's + If true, TOASTed values are checked against the target relation's TOAST table. - This option is known to be slow. Also, if the toast table or its - index is corrupt, checking it against toast values could conceivably + This option is known to be slow. Also, if the TOAST table or its + index is corrupt, checking it against TOAST values could conceivably crash the server, although in many cases this would just produce an error. @@ -514,8 +514,8 @@ SET client_min_messages = DEBUG1; Relation pages which are correctly formatted, internally consistent, and correct relative to their own internal checksums may still contain logical corruption. As such, this kind of corruption cannot be detected - with checksums. Examples include toasted - values in the main table which lack a corresponding entry in the toast + with checksums. Examples include TOASTed + values in the main table which lack a corresponding entry in the TOAST table, and tuples in the main table with a Transaction ID that is older than the oldest valid Transaction ID in the database or cluster. diff --git a/doc/src/sgml/bki.sgml b/doc/src/sgml/bki.sgml index 3cd5bee..53a982b 100644 --- a/doc/src/sgml/bki.sgml +++ b/doc/src/sgml/bki.sgml @@ -1042,7 +1042,7 @@ $ perl rewrite_dat_with_prokind.pl pg_proc.dat - Define indexes and toast tables. + Define indexes and TOAST tables. diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index 238ed67..63e8aa2 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -1954,7 +1954,7 @@ SCRAM-SHA-256$<iteration count>:&l The OID of the data type that corresponds to this table's row type, - if any; zero for indexes, sequences, and toast tables, which have + if any; zero for indexes, sequences, and TOAST tables, which have no pg_type entry @@ -9434,7 +9434,7 @@ SCRAM-SHA-256$<iteration count>:&l typstorage tells for varlena types (those with typlen = -1) if - the type is prepared for toasting and what the default strategy + the type is prepared for TOASTing and what the default strategy for attributes of this type should be. Possible values are: @@ -9464,7 +9464,7 @@ SCRAM-SHA-256$<iteration count>:&l - x is the usual choice for toast-able types. + x is the usual choice for TOAST-able types. Note that m values can also be moved out to secondary storage, but only as a last resort (e and x values are moved first). diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index 8290cd1..1811617 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -1738,7 +1738,7 @@ DETAIL: detailed_explanation. The remote tuple section includes the new tuple from the remote insert or update operation that caused the conflict. Note that for an update operation, the column value of the new tuple will be null - if the value is unchanged and toasted. + if the value is unchanged and TOASTed. diff --git a/doc/src/sgml/logicaldecoding.sgml b/doc/src/sgml/logicaldecoding.sgml index 1c4ae38..ea65a4a 100644 --- a/doc/src/sgml/logicaldecoding.sgml +++ b/doc/src/sgml/logicaldecoding.sgml @@ -1368,7 +1368,7 @@ commit_prepared_cb(...); <-- commit of the prepared transaction currently used for decoded changes) is selected and streamed. However, in some cases we still have to spill to disk even if streaming is enabled because we exceed the memory threshold but still have not decoded the - complete tuple e.g., only decoded toast table insert but not the main table + complete tuple e.g., only decoded TOAST table insert but not the main table insert. diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml index 938450f..0c462d2 100644 --- a/doc/src/sgml/ref/alter_table.sgml +++ b/doc/src/sgml/ref/alter_table.sgml @@ -825,7 +825,7 @@ WITH ( MODULUS numeric_literal, REM SHARE UPDATE EXCLUSIVE lock will be taken for - fillfactor, toast and autovacuum storage parameters, as well as the + fillfactor, TOAST and autovacuum storage parameters, as well as the planner parameter parallel_workers. diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 2237321..73fc8e3 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -1592,7 +1592,7 @@ WITH ( MODULUS numeric_literal, REM The toast_tuple_target specifies the minimum tuple length required before we try to compress and/or move long column values into TOAST tables, and - is also the target length we try to reduce the length below once toasting + is also the target length we try to reduce the length below once TOASTing begins. This affects columns marked as External (for move), Main (for compression), or Extended (for both) and applies only to new tuples. There is no effect on existing rows. diff --git a/doc/src/sgml/ref/create_type.sgml b/doc/src/sgml/ref/create_type.sgml index 994dfc6..a491914 100644 --- a/doc/src/sgml/ref/create_type.sgml +++ b/doc/src/sgml/ref/create_type.sgml @@ -411,10 +411,10 @@ CREATE TYPE name All storage values other than plain imply that the functions of the data type - can handle values that have been toasted, as described + can handle values that have been TOASTed, as described in and . The specific other value given merely determines the default TOAST - storage strategy for columns of a toastable data type; users can pick + storage strategy for columns of a TOAST-able data type; users can pick other strategies for individual columns using ALTER TABLE SET STORAGE. diff --git a/doc/src/sgml/ref/pg_amcheck.sgml b/doc/src/sgml/ref/pg_amcheck.sgml index 6bfe287..ef2bdfd 100644 --- a/doc/src/sgml/ref/pg_amcheck.sgml +++ b/doc/src/sgml/ref/pg_amcheck.sgml @@ -41,7 +41,7 @@ PostgreSQL documentation - Only ordinary and toast table relations, materialized views, sequences, and + Only ordinary and TOAST table relations, materialized views, sequences, and btree indexes are currently supported. Other relation types are silently skipped. @@ -276,7 +276,7 @@ PostgreSQL documentation - By default, if a table is checked, its toast table, if any, will also + By default, if a table is checked, its TOAST table, if any, will also be checked, even if it is not explicitly selected by an option such as --table or --relation. This option suppresses that behavior. @@ -306,9 +306,9 @@ PostgreSQL documentation - By default, whenever a toast pointer is encountered in a table, + By default, whenever a TOAST pointer is encountered in a table, a lookup is performed to ensure that it references apparently-valid - entries in the toast table. These checks can be quite slow, and this + entries in the TOAST table. These checks can be quite slow, and this option can be used to skip them. @@ -368,9 +368,9 @@ PostgreSQL documentation End checking at the specified block number. An error will occur if the table relation being checked has fewer than this number of blocks. This option does not apply to indexes, and is probably only useful when - checking a single table relation. If both a regular table and a toast + checking a single table relation. If both a regular table and a TOAST table are checked, this option will apply to both, but higher-numbered - toast blocks may still be accessed while validating toast pointers, + TOAST blocks may still be accessed while validating TOAST pointers, unless that is suppressed using . diff --git a/doc/src/sgml/sepgsql.sgml b/doc/src/sgml/sepgsql.sgml index ca038d7..eab5fde 100644 --- a/doc/src/sgml/sepgsql.sgml +++ b/doc/src/sgml/sepgsql.sgml @@ -433,7 +433,7 @@ UPDATE t1 SET x = 2, y = func1(y) WHERE z = 100; The default database privilege system allows database superusers to modify system catalogs using DML commands, and reference or modify - toast tables. These operations are prohibited when + TOAST tables. These operations are prohibited when sepgsql is enabled. diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml index af7864a..69747d0 100644 --- a/doc/src/sgml/xfunc.sgml +++ b/doc/src/sgml/xfunc.sgml @@ -2555,7 +2555,7 @@ CREATE FUNCTION concat_text(text, text) RETURNS text to be just pointless obscurantism, compared to using plain C calling conventions. They do however allow us to deal with NULLable arguments/return values, - and toasted (compressed or out-of-line) values. + and TOASTed (compressed or out-of-line) values. diff --git a/doc/src/sgml/xtypes.sgml b/doc/src/sgml/xtypes.sgml index e67e5bd..13af113 100644 --- a/doc/src/sgml/xtypes.sgml +++ b/doc/src/sgml/xtypes.sgml @@ -267,7 +267,7 @@ CREATE TYPE complex ( To support TOAST storage, the C functions operating on the data - type must always be careful to unpack any toasted values they are handed + type must always be careful to unpack any TOASTed values they are handed by using PG_DETOAST_DATUM. (This detail is customarily hidden by defining type-specific GETARG_DATATYPE_P macros.) Then, when running the CREATE TYPE command, specify the -- 1.8.3.1