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

Commit4dd4e3f

Browse files
committed
Correct thinko in last-minute release note item.
The CREATE INDEX CONCURRENTLY bug can only be triggered by row updates,not inserts, since the problem would arise from an update incorrectlybeing made HOT. Noted by Alvaro.
1 parent6f5e809 commit4dd4e3f

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

‎doc/src/sgml/release-9.2.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,8 +49,8 @@
4949

5050
<para>
5151
If <command>CREATE INDEX CONCURRENTLY</> was used to build an index
52-
that depends on a column not previously indexed, then rows inserted
53-
orupdated by transactions that ran concurrently with
52+
that depends on a column not previously indexed, then rows
53+
updated by transactions that ran concurrently with
5454
the <command>CREATE INDEX</> command could have received incorrect
5555
index entries. If you suspect this may have happened, the most
5656
reliable solution is to rebuild affected indexes after installing

‎doc/src/sgml/release-9.3.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,8 +49,8 @@
4949

5050
<para>
5151
If <command>CREATE INDEX CONCURRENTLY</> was used to build an index
52-
that depends on a column not previously indexed, then rows inserted
53-
orupdated by transactions that ran concurrently with
52+
that depends on a column not previously indexed, then rows
53+
updated by transactions that ran concurrently with
5454
the <command>CREATE INDEX</> command could have received incorrect
5555
index entries. If you suspect this may have happened, the most
5656
reliable solution is to rebuild affected indexes after installing

0 commit comments

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