Re: Typo in the comment above heap_prepare_freeze_tuple() - Mailing list pgsql-hackers

From Amit Langote
Subject Re: Typo in the comment above heap_prepare_freeze_tuple()
Date
Msg-id 56775864.1010806@lab.ntt.co.jp
Whole thread Raw
In response to Re: Typo in the comment above heap_prepare_freeze_tuple()  (Robert Haas <robertmhaas@gmail.com>)
List 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@lab.ntt.co.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






pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Optimizing away second VACUUM heap scan when only BRIN indexes on table
Next
From: Alvaro Herrera
Date:
Subject: Re: Optimizing away second VACUUM heap scan when only BRIN indexes on table