Alvaro Herrera <[EMAIL PROTECTED]> writes:
> 1. To examine a tuple one must first call LockTuple, which grabs a pin
> and lock in the buffer.  The buffer lock is released right away, but the
> pin is kept.

Surely you don't mean that *every* access to a tuple now has to go
through the lock manager :-(.  Have you done any performance testing?

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to