summaryrefslogtreecommitdiff
path: root/src/backend/access/heap/README.tuplock
diff options
context:
space:
mode:
Diffstat (limited to 'src/backend/access/heap/README.tuplock')
-rw-r--r--src/backend/access/heap/README.tuplock4
1 files changed, 1 insertions, 3 deletions
diff --git a/src/backend/access/heap/README.tuplock b/src/backend/access/heap/README.tuplock
index 818cd7f9806..31c52ad28f9 100644
--- a/src/backend/access/heap/README.tuplock
+++ b/src/backend/access/heap/README.tuplock
@@ -203,6 +203,4 @@ Inplace updates create an exception to the rule that tuple data won't change
under a reader holding a pin. A reader of a heap_fetch() result tuple may
witness a torn read. Current inplace-updated fields are aligned and are no
wider than four bytes, and current readers don't need consistency across
-fields. Hence, they get by with just fetching each field once. XXX such a
-caller may also read a value that has not reached WAL; see
-systable_inplace_update_finish().
+fields. Hence, they get by with just fetching each field once.