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:48:25 -0400 |
| commit | 9cc510fe89a3f013091bf7234ca893ba74a15094 (patch) | |
| tree | e5ee8fe9f667c459f72f2eae5338f464f20057ce /src | |
| parent | 029386ccbddd0a33d481b94e511f5219b03e6636 (diff) | |
| download | postgresql-9cc510fe89a3f013091bf7234ca893ba74a15094.tar.gz postgresql-9cc510fe89a3f013091bf7234ca893ba74a15094.zip | |
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 23139e46cbb..e6caa4e9b6c 100644 --- a/src/backend/access/heap/heapam.c +++ b/src/backend/access/heap/heapam.c @@ -3706,7 +3706,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 @@ -3718,8 +3718,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, |