@@ -963,11 +963,10 @@ btvacuumscan(IndexVacuumInfo *info, IndexBulkDeleteResult *stats,
963963 * recycled. Taking the lock synchronizes things enough to prevent a
964964 * problem: either num_pages won't include the new page, or _bt_getbuf
965965 * already has write lock on the buffer and it will be fully initialized
966- * before we can examine it. (See also vacuumlazy.c, which has the same
967- * issue.)Also, we need not worry if a page is added immediately after
968- * we look; the page splitting code already has write-lock on the left
969- * page before it adds a right page, so we must already have processed any
970- * tuples due to be moved into such a page.
966+ * before we can examine it. Also, we need not worry if a page is added
967+ * immediately after we look; the page splitting code already has
968+ * write-lock on the left page before it adds a right page, so we must
969+ * already have processed any tuples due to be moved into such a page.
971970 *
972971 * We can skip locking for new or temp relations, however, since no one
973972 * else could be accessing them.