Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit073d7cb

Browse files
Fix docs on lock level for ALTER TABLE VALIDATE
ALTER TABLE .. VALIDATE CONSTRAINT previouslygave incorrect details about lock levels andtherefore incomplete reasons to use the option.Initial bug report and fix from Marko TiikkajaReworded by me to include comments by Kevin Grittner
1 parentc3c86ae commit073d7cb

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

‎doc/src/sgml/ref/alter_table.sgml

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -324,9 +324,13 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable>
324324
as <literal>NOT VALID</literal>, by scanning the table to ensure there
325325
are no rows for which the constraint is not satisfied.
326326
Nothing happens if the constraint is already marked valid.
327-
The value of separating validation from initial creation of the
328-
constraint is that validation requires a lesser lock on the table
329-
than constraint creation does.
327+
</para>
328+
<para>
329+
Validation can be a long process on larger tables and currently requires
330+
an <literal>ACCESS EXCLUSIVE</literal> lock. The value of separating
331+
validation from initial creation is that you can defer validation to less
332+
busy times, or can be used to give additional time to correct pre-existing
333+
errors while preventing new errors.
330334
</para>
331335
</listitem>
332336
</varlistentry>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp