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 | 1924ef41668773ad62d845eebc11ff35f17446ad (patch) | |
| tree | 1b897034d787523d00928227bb60564b93aea905 | |
| parent | eca2f8a7dd9bda862a25fcc57ddf77f7c0dc3afe (diff) | |
| download | postgresql-1924ef41668773ad62d845eebc11ff35f17446ad.tar.gz postgresql-1924ef41668773ad62d845eebc11ff35f17446ad.zip | |
Reword some unclear comments
| -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 84b59c34100..4327be86100 100644 --- a/src/backend/access/heap/heapam.c +++ b/src/backend/access/heap/heapam.c @@ -3930,7 +3930,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 @@ -3942,8 +3942,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, |