[ pgsql-general removed from cc list, as this is quite inappropriate
there ]
Jenny - [EMAIL PROTECTED] writes:
I am working on a project that involves displaying locking information about
each lock taken, whether it be a row level or table leve llock.
When dealing with struct LOCK
On Thu, Sep 04, 2003 at 08:56:31AM -0700, Jenny - wrote:
I am working on a project that involves displaying locking information
about each lock taken, whether it be a row level or table leve llock.
When dealing with struct LOCK (src/include/storage) i have noticed that
postgreSQL creates a
On Thu, Sep 04, 2003 at 11:21:05AM -0700, Jenny - wrote:
I think the locks would actually by represented by PROCLOCK structures.
The LOCK structures are for lockable objects, not for actual locks.
Well,from what i understand, PROCLOCK stores the TransactionID and the LOCK
its holding lock
Alvaro Herrera Munoz [EMAIL PROTECTED] writes:
Anyway, I think the LOCK structure represents something that can be locked.
Right.
The PROCLOCK struct represents that some process is holding a lock on said
object.
IIRC, a PROCLOCK is created as soon as some backend tries to lock some
lockable
I am working on a project that involves displaying locking information about
each lock taken, whether it be a row level or table leve llock.
When dealing with struct LOCK (src/include/storage) i have noticed that
postgreSQL creates a single LOCK struct for each table in the db. Like if
i
On Thu, Sep 04, 2003 at 08:56:31AM -0700, Jenny - wrote:
I am working on a project that involves displaying locking information
about each lock taken, whether it be a row level or table leve llock.
When dealing with struct LOCK (src/include/storage) i have noticed that
postgreSQL creates a
