From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Typo in the comment above heap_prepare_freeze_tuple() |
Date: | 2015-12-21 01:39:48 |
Message-ID: | 56775864.1010806@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2015/12/19 2:05, Robert Haas wrote:
> On Fri, Dec 18, 2015 at 1:25 AM, Amit Langote
> <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>> 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.
>
> Committed.
Thanks!
Regards,
Amit
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-12-21 02:14:46 | Re: Optimizing away second VACUUM heap scan when only BRIN indexes on table |
Previous Message | Jim Nasby | 2015-12-21 01:13:25 | Re: Optimizing away second VACUUM heap scan when only BRIN indexes on table |