Typo in the comment above heap_prepare_freeze_tuple()

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Typo in the comment above heap_prepare_freeze_tuple()
Date: 2015-12-18 06:25:53
Message-ID: 5673A6F1.9060709@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I think the following may be a typo:

* 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).

If so, attached is the patch.

Thanks,
Amit

Attachment Content-Type Size
comment-typo-heap_prepare_freeze_tuple.patch text/x-diff 747 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2015-12-18 06:47:09 Re: Comment typo in pg_upgrade.c
Previous Message Michael Paquier 2015-12-18 06:22:23 Re: Freeze avoidance of very large table.