Re: heap_freeze_tuple locking requirements
Alvaro Herrera <alvherre@commandprompt.com>
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-03-23T15:02:18Z
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@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support