diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2017-08-08 18:46:16 -0400 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2017-08-08 18:49:23 -0400 |
| commit | 962b26b674d29fa2834afbd760a9229bc42a5876 (patch) | |
| tree | aec7f889f31d5bf69d31e99de28496f12edc3def /src | |
| parent | a5915db2fab1fbe555b6410440df5177a247a2f2 (diff) | |
Reword some unclear comments
Diffstat (limited to 'src')
| -rw-r--r-- | src/backend/access/heap/heapam.c | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/src/backend/access/heap/heapam.c b/src/backend/access/heap/heapam.c index 310ef048ead..f5db3c775c3 100644 --- a/src/backend/access/heap/heapam.c +++ b/src/backend/access/heap/heapam.c @@ -3443,7 +3443,7 @@ l2: /* * To prevent concurrent sessions from updating the tuple, we have to - * temporarily mark it locked, while we release the lock. + * temporarily mark it locked, while we release the page-level lock. * * To satisfy the rule that any xid potentially appearing in a buffer * written out to disk, we unfortunately have to WAL log this @@ -3455,8 +3455,9 @@ l2: /* * Compute xmax / infomask appropriate for locking the tuple. This has - * to be done separately from the lock, because the potentially - * created multixact would otherwise be wrong. + * to be done separately from the combo that's going to be used for + * updating, because the potentially created multixact would otherwise + * be wrong. */ compute_new_xmax_infomask(HeapTupleHeaderGetRawXmax(oldtup.t_data), oldtup.t_data->t_infomask, |