From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Sumaira Ali" <nat_lazy(at)hotmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: lock.h and proc.h |
Date: | 2003-02-06 15:19:12 |
Message-ID: | 12445.1044544752@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
"Sumaira Ali" <nat_lazy(at)hotmail(dot)com> writes:
> hi..i have questions about struct pgproc (in file proc.h) and proclock ( in
> file lock.h) of the postgresql source code, does anyone know the exact
> difference between pgproc and proclock structs??
There's one PGPROC per process. There's one PROCLOCK for each process
and each lock that that process has any interest in (ie, either
currently holds or is waiting for).
The comments for these structs seem to be a bit of a mess at the moment :-(
Bruce renamed the struct types recently, but appears not to have done a
good job of adjusting the comments to match. It may help to know that
a proclock object was formerly called a "holder".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2003-02-06 16:00:59 | Re: Status report: regex replacement |
Previous Message | Tatsuo Ishii | 2003-02-06 15:05:03 | Re: Status report: regex replacement |
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Drokin | 2003-02-08 17:32:17 | trivial patch for pg_dump blob problem |
Previous Message | John Cochran | 2003-02-06 01:42:14 | Patch to extend range of timestamps |