mirror of
https://github.com/postgres/postgres.git
synced 2025-08-05 07:41:25 +03:00
Support amcheck of sequences
Sequences were left out of the list of relation kinds that verify_heapam knew how to check, though it is fairly trivial to allow them. Doing that, and while at it, updating pg_amcheck to include sequences in relations matched by table and relation patterns. Author: Mark Dilger <mark.dilger@enterprisedb.com> Discussion: https://www.postgresql.org/message-id/flat/81ad4757-92c1-4aa3-7bee-f609544837e3%40enterprisedb.com
This commit is contained in:
@@ -220,10 +220,10 @@ SET client_min_messages = DEBUG1;
|
||||
</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Checks a table for structural corruption, where pages in the relation
|
||||
contain data that is invalidly formatted, and for logical corruption,
|
||||
where pages are structurally valid but inconsistent with the rest of the
|
||||
database cluster.
|
||||
Checks a table, sequence, or materialized view for structural corruption,
|
||||
where pages in the relation contain data that is invalidly formatted, and
|
||||
for logical corruption, where pages are structurally valid but
|
||||
inconsistent with the rest of the database cluster.
|
||||
</para>
|
||||
<para>
|
||||
The following optional arguments are recognized:
|
||||
|
@@ -41,8 +41,9 @@ PostgreSQL documentation
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Only table relations and btree indexes are currently supported. Other
|
||||
relation types are silently skipped.
|
||||
Only ordinary and toast table relations, materialized views, sequences, and
|
||||
btree indexes are currently supported. Other relation types are silently
|
||||
skipped.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@@ -124,7 +125,7 @@ PostgreSQL documentation
|
||||
</para>
|
||||
<para>
|
||||
This is similar to the <option>--relation</option> option, except that
|
||||
it applies only to indexes, not tables.
|
||||
it applies only to indexes, not to other relation types.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
@@ -140,7 +141,7 @@ PostgreSQL documentation
|
||||
</para>
|
||||
<para>
|
||||
This is similar to the <option>--exclude-relation</option> option,
|
||||
except that it applies only to indexes, not tables.
|
||||
except that it applies only to indexes, not other relation types.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
@@ -236,7 +237,8 @@ PostgreSQL documentation
|
||||
</para>
|
||||
<para>
|
||||
This is similar to the <option>--relation</option> option, except that
|
||||
it applies only to tables, not indexes.
|
||||
it applies only to tables, materialized views, and sequences, not to
|
||||
indexes.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
@@ -252,7 +254,8 @@ PostgreSQL documentation
|
||||
</para>
|
||||
<para>
|
||||
This is similar to the <option>--exclude-relation</option> option,
|
||||
except that it applies only to tables, not indexes.
|
||||
except that it applies only to tables, materialized views, and
|
||||
sequences, not to indexes.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
Reference in New Issue
Block a user