Re: heap_freeze_tuple locking requirements

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: heap_freeze_tuple locking requirements
Date: 2012-03-26 15:06:18
Message-ID: CA+TgmoZT1WEjt9Sn=DrmpKRT2L2A1CocwoJvdoWwsqoaoMe9+w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 23, 2012 at 11:02 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hans-Jürgen Schönig 2012-03-26 15:16:42 Re: Odd out of memory problem.
Previous Message Andrew Dunstan 2012-03-26 15:03:45 Odd out of memory problem.