[HACKERS] row level lock and table level locks

>A row lock is represented by storing the locking transaction's ID in xmax and setting >the HEAP_MARKED_FOR_UPDATE infomask bit. The bit is needed to distinguish  >this from the case where the transaction is deleting the tuple.Is there a similar bit modified if the row in question is being waited

Re: [HACKERS] row level lock and table level locks

Is there a array or some sort of datastructures that store all the HeapTupleDatas for all rows in the db? like we have the LockData storing all the current locks in the db. thanks!Tom Lane <[EMAIL PROTECTED]> wrote: Larry Douzie <[EMAIL PROTECTED]>writes:>> A row lock is represen

Re: [HACKERS] row level lock and table level locks

Larry Douzie <[EMAIL PROTECTED]>writes:> Is there a array or some sort of datastructures that store all the> HeapTupleDatas for all rows in the db?Er, wouldn't that be the database files? What i mean is, whats the pointer name to this list of HeapTupleDatas?Tom Lane <[EMA