Re: heap_freeze_tuple locking requirements - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: heap_freeze_tuple locking requirements
Date
Msg-id 1332514761-sup-3760@alvh.no-ip.org
Whole thread Raw
In response to heap_freeze_tuple locking requirements  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: heap_freeze_tuple locking requirements  (Robert Haas <robertmhaas@gmail.com>)
List 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@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Add notion of a "transform function" that can simplify function
Next
From: Peter Geoghegan
Date:
Subject: Re: Uppercase tab completion keywords in psql?