Re: heap_lock_updated_tuple_rec can leak a buffer refcount - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: heap_lock_updated_tuple_rec can leak a buffer refcount
Date
Msg-id CAA4eK1JvyFx9wy_6UBCAcMi94nNtRZnk_1eenyvwex4Oy9dBzA@mail.gmail.com
Whole thread Raw
In response to Re: heap_lock_updated_tuple_rec can leak a buffer refcount  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, Mar 3, 2018 at 3:26 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Alexander Kuzmenkov <a.kuzmenkov@postgrespro.ru> writes:
>> Looks like a leak indeed, the fix seems right.
>
>
> Hence, I propose the attached patch.  The test lobotomization
> (the "if (1) //" change) isn't meant for commit but shows how I tested
> the take-the-pin paths.  This passes make check-world with or without
> the lobotomization change.
>

Thanks for taking care of this.


-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: non-bulk inserts and tuple routing
Next
From: Andres Freund
Date:
Subject: Re: non-bulk inserts and tuple routing