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

Commit7b1053a

Browse files
committed
doc: mention unusability of dropped CHECK to verify NOT NULL
It's possible to use a CHECK (col IS NOT NULL) constraint to skipscanning a table for nulls when adding a NOT NULL constraint on the samecolumn. However, if the CHECK constraint is dropped on the same commandthat the NOT NULL is added, this fails, i.e., makes the NOT NULL additionslow. The best we can do about it at this stage is to document this sothat users aren't taken by surprise.(In Postgres 18 you can directly add the NOT NULL constraint as NOTVALID instead, so there's no longer much use for the CHECK constraint,therefore no point in building mechanism to support the case better.)Reported-by: Andrew <psy2000usa@yahoo.com>Reviewed-by: David G. Johnston <david.g.johnston@gmail.com>Discussion:https://postgr.es/m/175385113607.786.16774570234342968908@wrigleys.postgresql.org
1 parentfee46ab commit7b1053a

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

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

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -240,9 +240,10 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
240240
provided none of the records in the table contain a
241241
<literal>NULL</literal> value for the column. Ordinarily this is
242242
checked during the <literal>ALTER TABLE</literal> by scanning the
243-
entire table; however, if a valid <literal>CHECK</literal> constraint is
244-
found which proves no <literal>NULL</literal> can exist, then the
245-
table scan is skipped.
243+
entire table, unless <literal>NOT VALID</literal> is specified;
244+
however, if a valid <literal>CHECK</literal> constraint exists
245+
(and is not dropped in the same command) which proves no
246+
<literal>NULL</literal> can exist, then the table scan is skipped.
246247
If a column has an invalid not-null constraint,
247248
<literal>SET NOT NULL</literal> validates it.
248249
</para>

0 commit comments

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