Re: heap_freeze_tuple locking requirements

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: heap_freeze_tuple locking requirements
Date: 2012-03-23 15:02:18
Message-ID: 1332514761-sup-3760@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


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

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2012-03-23 15:07:24 Re: Uppercase tab completion keywords in psql?
Previous Message Tom Lane 2012-03-23 14:55:52 Re: [COMMITTERS] pgsql: Add notion of a "transform function" that can simplify function