Re: heap_freeze_tuple locking requirements

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-03-26T15:06:18Z
Lists: pgsql-hackers
On Fri, Mar 23, 2012 at 11:02 AM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> Excerpts from Robert Haas's message of mié mar 21 21:50:24 -0300 2012:
>> heap_freeze_tuple() was apparently designed at one point to cope with
>> being called with either a shared or exclusive buffer lock.  But none
>> of the current callers call it with a shared lock; they all call it
>> with an exclusive lock, except for the heap-rewrite code which doesn't
>> take (or need) a lock at all.
>
>> Since this is just dead code removal, I propose to apply this to 9.2.
>
> +1

Thanks, done.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company