Thread: Typo in the comment above heap_prepare_freeze_tuple()
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
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. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
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