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

Commit24b1f14

Browse files
committed
Clarify wording on when ctid is modified by VACUUM FULL.
1 parentcd44c23 commit24b1f14

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

‎doc/src/sgml/ddl.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.70 2006/12/28 20:02:38 tgl Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.71 2006/12/30 20:31:11 momjian Exp $ -->
22

33
<chapter id="ddl">
44
<title>Data Definition</title>
@@ -974,7 +974,7 @@ CREATE TABLE order_items (
974974
The physical location of the row version within its table. Note that
975975
although the <structfield>ctid</structfield> can be used to
976976
locate the row version very quickly, a row's
977-
<structfield>ctid</structfield> will changeeach time it is
977+
<structfield>ctid</structfield> will changeif it is
978978
updated or moved by <command>VACUUM FULL</>. Therefore
979979
<structfield>ctid</structfield> is useless as a long-term row
980980
identifier. The OID, or even better a user-defined serial

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp