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:24 -0400 |
| commit | e829db0b19bda06996a1c7104ca1251c8eacaa2c (patch) | |
| tree | 084686431006e009a65575a258d7dfdb82ece512 /src/backend/access | |
| parent | 6d81d0a215a5b843bf003b0a1c4b43f6d2cccc78 (diff) | |
| download | postgresql-e829db0b19bda06996a1c7104ca1251c8eacaa2c.tar.gz postgresql-e829db0b19bda06996a1c7104ca1251c8eacaa2c.zip | |
Reword some unclear comments
Diffstat (limited to 'src/backend/access')
| -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 26d96fd7fc0..af101689282 100644 --- a/src/backend/access/heap/heapam.c +++ b/src/backend/access/heap/heapam.c @@ -3594,7 +3594,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 @@ -3606,8 +3606,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, |