diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index 85084a7c233..508bea3bc64 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -1966,9 +1966,9 @@ SCRAM-SHA-256$<iteration count>:&l Size of the on-disk representation of this table in pages (of size BLCKSZ). This is only an estimate used by the - planner. It is updated by VACUUM, - ANALYZE, and a few DDL commands such as - CREATE INDEX. + planner. It is updated by , + , and a few DDL commands such as + . @@ -1978,9 +1978,9 @@ SCRAM-SHA-256$<iteration count>:&l Number of live rows in the table. This is only an estimate used by - the planner. It is updated by VACUUM, - ANALYZE, and a few DDL commands such as - CREATE INDEX. + the planner. It is updated by , + , and a few DDL commands such as + . If the table has never yet been vacuumed or analyzed, reltuples contains -1 indicating that the row count is @@ -1995,9 +1995,9 @@ SCRAM-SHA-256$<iteration count>:&l Number of pages that are marked all-visible in the table's visibility map. This is only an estimate used by the - planner. It is updated by VACUUM, - ANALYZE, and a few DDL commands such as - CREATE INDEX. + planner. It is updated by , + , and a few DDL commands such as + . @@ -2241,8 +2241,8 @@ SCRAM-SHA-256$<iteration count>:&l lazily: they are guaranteed to be true if that's the correct state, but may not be reset to false immediately when the condition is no longer true. For example, relhasindex is set by - CREATE INDEX, but it is never cleared by - DROP INDEX. Instead, VACUUM clears + , but it is never cleared by + . Instead, clears relhasindex if it finds the table has no indexes. This arrangement avoids race conditions and improves concurrency. @@ -2419,8 +2419,8 @@ SCRAM-SHA-256$<iteration count>:&l - User-defined constraint triggers (created with CREATE CONSTRAINT - TRIGGER) also give rise to an entry in this table. + User-defined constraint triggers (created with + CREATE CONSTRAINT TRIGGER) also give rise to an entry in this table. @@ -3425,7 +3425,7 @@ SCRAM-SHA-256$<iteration count>:&l the referenced object (see pg_extension). The dependent object can be dropped only via - DROP EXTENSION on the referenced object. + on the referenced object. Functionally this dependency type acts the same as an INTERNAL dependency, but it's kept separate for clarity and to simplify pg_dump. @@ -3456,7 +3456,7 @@ SCRAM-SHA-256$<iteration count>:&l There is no dependent object; this type of entry is a signal that the system itself depends on the referenced object, and so that object must never be deleted. Entries of this type are - created only by initdb. The columns for the + created only by initdb. The columns for the dependent object contain zeroes. @@ -4285,7 +4285,7 @@ SCRAM-SHA-256$<iteration count>:&l If true, the index is currently valid for queries. False means the index is possibly incomplete: it must still be modified by - INSERT/UPDATE operations, but it cannot safely + / operations, but it cannot safely be used for queries. If it is unique, the uniqueness property is not guaranteed true either. @@ -4309,7 +4309,7 @@ SCRAM-SHA-256$<iteration count>:&l If true, the index is currently ready for inserts. False means the - index must be ignored by INSERT/UPDATE + index must be ignored by / operations. @@ -4330,8 +4330,8 @@ SCRAM-SHA-256$<iteration count>:&l If true this index has been chosen as replica identity - using ALTER TABLE ... REPLICA IDENTITY USING INDEX - ... + using ALTER TABLE ... + REPLICA IDENTITY USING INDEX ... @@ -4504,11 +4504,11 @@ SCRAM-SHA-256$<iteration count>:&l Objects can have initial privileges either by having those privileges set when the system is initialized (by initdb) or when the - object is created during a CREATE EXTENSION and the - extension script sets initial privileges using the GRANT + object is created during a and the + extension script sets initial privileges using the system. Note that the system will automatically handle recording of the privileges during the extension script and that extension authors need - only use the GRANT and REVOKE + only use the and statements in their script to have the privileges recorded. The privtype column indicates if the initial privilege was set by initdb or during a @@ -5564,10 +5564,10 @@ SCRAM-SHA-256$<iteration count>:&l The command type to which the policy is applied: - r for SELECT, - a for INSERT, - w for UPDATE, - d for DELETE, + r for , + a for , + w for , + d for , or * for all @@ -6075,7 +6075,7 @@ SCRAM-SHA-256$<iteration count>:&l pubinsert bool - If true, INSERT operations are replicated for + If true, operations are replicated for tables in the publication. @@ -6085,7 +6085,7 @@ SCRAM-SHA-256$<iteration count>:&l pubupdate bool - If true, UPDATE operations are replicated for + If true, operations are replicated for tables in the publication. @@ -6095,7 +6095,7 @@ SCRAM-SHA-256$<iteration count>:&l pubdelete bool - If true, DELETE operations are replicated for + If true, operations are replicated for tables in the publication. @@ -6105,7 +6105,7 @@ SCRAM-SHA-256$<iteration count>:&l pubtruncate bool - If true, TRUNCATE operations are replicated for + If true, operations are replicated for tables in the publication. @@ -6408,9 +6408,9 @@ SCRAM-SHA-256$<iteration count>:&l ev_type char - Event type that the rule is for: 1 = SELECT, 2 = - UPDATE, 3 = INSERT, 4 = - DELETE + Event type that the rule is for: 1 = , 2 = + , 3 = , 4 = + @@ -6832,7 +6832,7 @@ SCRAM-SHA-256$<iteration count>:&l There is no dependent object; this type of entry is a signal that the system itself depends on the referenced object, and so that object must never be deleted. Entries of this type are - created only by initdb. The columns for the + created only by initdb. The columns for the dependent object contain zeroes. @@ -7336,9 +7336,9 @@ SCRAM-SHA-256$<iteration count>:&l The pg_statistic_ext entry is filled in - completely during CREATE STATISTICS, but the actual + completely during , but the actual statistical values are not computed then. - Subsequent ANALYZE commands compute the desired values + Subsequent commands compute the desired values and populate an entry in the pg_statistic_ext_data catalog. @@ -7590,8 +7590,9 @@ SCRAM-SHA-256$<iteration count>:&l This catalog only contains tables known to the subscription after running - either CREATE SUBSCRIPTION or - ALTER SUBSCRIPTION ... REFRESH PUBLICATION. + either or + ALTER SUBSCRIPTION ... REFRESH + PUBLICATION. @@ -8837,7 +8838,7 @@ SCRAM-SHA-256$<iteration count>:&l (references pg_proc.oid) - Custom ANALYZE function, or 0 to use the standard function + Custom function, or 0 to use the standard function @@ -10324,7 +10325,7 @@ SCRAM-SHA-256$<iteration count>:&l indexdef text - Index definition (a reconstructed CREATE INDEX + Index definition (a reconstructed command) @@ -10779,7 +10780,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx definition text - Materialized view definition (a reconstructed SELECT query) + Materialized view definition (a reconstructed query) @@ -10949,7 +10950,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx The query string submitted by the client to create this prepared statement. For prepared statements created via SQL, - this is the PREPARE statement submitted by + this is the statement submitted by the client. For prepared statements created via the frontend/backend protocol, this is the text of the prepared statement itself. @@ -10983,7 +10984,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx true if the prepared statement was created - via the PREPARE SQL command; + via the SQL command; false if the statement was prepared via the frontend/backend protocol @@ -12114,7 +12115,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx reset_val text - Value that RESET would reset the parameter to + Value that would reset the parameter to in the current session @@ -12172,7 +12173,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx These settings cannot be changed directly; they reflect internally determined values. Some of them may be adjustable by rebuilding the server with different configuration options, or by changing options - supplied to initdb. + supplied to initdb. @@ -12247,7 +12248,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx These settings can be set from postgresql.conf, - or within a session via the SET command; but only superusers + or within a session via the command; but only superusers can change them via SET. Changes in postgresql.conf will affect existing sessions only if no session-local value has been established with SET. @@ -12260,7 +12261,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx These settings can be set from postgresql.conf, - or within a session via the SET command. Any user is + or within a session via the command. Any user is allowed to change their session-local value. Changes in postgresql.conf will affect existing sessions only if no session-local value has been established with SET. @@ -12276,7 +12277,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx The pg_settings view cannot be inserted into or - deleted from, but it can be updated. An UPDATE applied + deleted from, but it can be updated. An applied to a row of pg_settings is equivalent to executing the command on that named parameter. The change only affects the value used by the current @@ -12620,7 +12621,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx If greater than zero, the estimated number of distinct values in the column. If less than zero, the negative of the number of distinct values divided by the number of rows. (The negated form is used when - ANALYZE believes that the number of distinct values is + believes that the number of distinct values is likely to increase as the table grows; the positive form is used when the column seems to have a fixed number of possible values.) For example, -1 indicates a unique column in which the number of distinct @@ -12718,7 +12719,8 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx The maximum number of entries in the array fields can be controlled on a - column-by-column basis using the ALTER TABLE SET STATISTICS + column-by-column basis using the ALTER + TABLE SET STATISTICS command, or globally by setting the run-time parameter. @@ -12843,7 +12845,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx than zero, the estimated number of distinct values in the combination. If less than zero, the negative of the number of distinct values divided by the number of rows. - (The negated form is used when ANALYZE believes that + (The negated form is used when believes that the number of distinct values is likely to increase as the table grows; the positive form is used when the column seems to have a fixed number of possible values.) For example, -1 indicates a unique combination of @@ -12908,8 +12910,8 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx The maximum number of entries in the array fields can be controlled on a - column-by-column basis using the ALTER TABLE SET STATISTICS - command, or globally by setting the + column-by-column basis using the ALTER + TABLE SET STATISTICS command, or globally by setting the run-time parameter. @@ -13471,7 +13473,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx definition text - View definition (a reconstructed SELECT query) + View definition (a reconstructed query)