On 2015/12/19 2:05, Robert Haas wrote:
> On Fri, Dec 18, 2015 at 1:25 AM, Amit Langote
> 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
On Fri, Dec 18, 2015 at 1:25 AM, Amit Langote
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
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 (whi
