aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2015-12-18 12:03:15 -0500
committerRobert Haas <rhaas@postgresql.org>2015-12-18 12:03:15 -0500
commit9a51698bae86f748279ecedcae018925b5af5b2d (patch)
tree3223cbb4d58fe4c391e25ccb7a3d00b1b7d68e1b
parent9246af6799819847faa33baf441251003acbb8fe (diff)
downloadpostgresql-9a51698bae86f748279ecedcae018925b5af5b2d.tar.gz
postgresql-9a51698bae86f748279ecedcae018925b5af5b2d.zip
Fix typo in comment.
Amit Langote
-rw-r--r--src/backend/access/heap/heapam.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/access/heap/heapam.c b/src/backend/access/heap/heapam.c
index 9ff7a41e43c..3c2878b2d40 100644
--- a/src/backend/access/heap/heapam.c
+++ b/src/backend/access/heap/heapam.c
@@ -6547,7 +6547,7 @@ heap_prepare_freeze_tuple(HeapTupleHeader tuple, TransactionId cutoff_xid,
*
* Caller is responsible for ensuring that no other backend can access the
* storage underlying this tuple, either by holding an exclusive lock on the
- * buffer containing it (which is what lazy VACUUM does), or by having it by
+ * buffer containing it (which is what lazy VACUUM does), or by having it be
* in private storage (which is what CLUSTER and friends do).
*
* Note: it might seem we could make the changes without exclusive lock, since