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:01 -0400 |
| commit | 77d2c00af78ee12ae0d1cea34605f1e7af3f6d93 (patch) | |
| tree | 702b85c85351ac5a6089e2ecc3b3916a76b776d7 | |
| parent | f5d54ef97abdd1df3d6bfe0320a565ecce742abe (diff) | |
| download | postgresql-77d2c00af78ee12ae0d1cea34605f1e7af3f6d93.tar.gz postgresql-77d2c00af78ee12ae0d1cea34605f1e7af3f6d93.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 479c3843f01..e283fe5b1f5 100644 --- a/src/backend/access/heap/heapam.c +++ b/src/backend/access/heap/heapam.c @@ -3983,7 +3983,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 @@ -3995,8 +3995,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, |