Locks, more complicated than I orginally thought

From: Chris Humphries <chumphries(at)devis(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Locks, more complicated than I orginally thought
Date: 2002-01-28 08:46:35
Message-ID: 3C550FEB.2070501@devis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello all,
I am working on that SHOW locks todo item, that lists all
current locks. This seems a bit tricky as there is no central
place where one could reference a lock, appears they are just
called.
Now my question is that, would it be "ok" to have a locks
linked list that held all the locks, and their information
in the function calls that make the lock? Or is there some
other method that would be more suitable for this. Seeking
the advice of experience with this sorta thing (if there is
anyone, heh).
If there was this one master linked list, holding all the
lock information, then making a SHOW locks like command would
be a snap!
Also do you think this sort of action would slow the database
down too much to even warrent doing it this way? Of course i
personally havent tested yet, so have no figures, but you
guys know more about database programming and postgresql.

Thanks,
Chris

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vladimir Zamiussky 2002-01-28 09:12:08 Execution time of UPDATE raises dramatically!
Previous Message G.Nagarajan 2002-01-28 08:33:10 Re: Bad Timestamp Format