PGRPROC

Started by Sumaira Alialmost 23 years ago2 messages

nat_lazy@hotmail.com

almost 23 years ago

<html><div style='background-color:'><DIV>if pgproc is used to represent a process and proclock represents a process and its locks of interest, then why does pgproc contain the following information about locks?</DIV>
<DIV>
/*
* XLOG location of first XLOG record written by this backend's
* current transaction. If backend is not in a transaction or hasn't
* yet modified anything, logRec.xrecoff is zero.
*/
XLogRecPtr logRec;
/* Info about LWLock the process is currently waiting for, if any. */
bool lwWaiting; /* true if waiting for an LW lock */
bool lwExclusive; /* true if waiting for exclusive access */
struct PGPROC *lwWaitLink; /* next waiter for same LW lock */
/* Info about lock the process is currently waiting for, if any. */
/* waitLock and waitHolder are NULL if not currently waiting. */
LOCK *waitLock; /* Lock object we're sleeping on ... */
PROCLOCK *waitHolder; /* Per-holder info for awaited lock */
LOCKMODE waitLockMode; /* type of lock we're waiting for */
LOCKMASK heldLocks; /* bitmask for lock types already held on
* this lock object by this backend */
SHM_QUEUE procHolders; /* list of PROCLOCK objects for locks held
* or awaited by this backend */
};</DIV></div> <hr>MSN 8 with <a href="http://g.msn.com/8HMWENUS/2740">e-mail virus protection service: </a> 2 months FREE*</html>

Bruce Momjian

pgman@candle.pha.pa.us

almost 23 years ago

In reply to: Sumaira Ali (#1)

Re: PGRPROC

The proclock is structure links locks and procs, either for locks held,
or procs waiting for locks.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073