Re: obtaining row locking information

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: alvherre(at)alvh(dot)no-ip(dot)org
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, pgman(at)candle(dot)pha(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org
Subject: Re: obtaining row locking information
Date: 2005-08-20 00:08:54
Message-ID: 20050820.090854.39154716.t-ishii@sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Fri, Aug 19, 2005 at 09:19:24PM +0900, Tatsuo Ishii wrote:
> > > Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> > > > To accomplish this I need to add following function into
> > > > storage/ipc/procarray.c. This is similar to BackendPidGetProc() except
> > > > that it accepts xid as an argument. Any objection?
>
> I don't think it is critical for it to return valid answers for
> subtransactions, but maybe you should add a note in the commentary about
> it:
>
> > /*
> > * BackendXidGetPid -- get a backend's pid given its XID
> > *
> > * Returns 0 if not found or it's a prepared transaction. Note that
> > * it is up to the caller to be sure that the question remains
> > * meaningful for long enough for the answer to be used ...
> *
> * Only main transaction Ids are considered. This function is mainly
> * useful for determining what backend owns a lock.
> > */
> > int
> > BackendXidGetPid(TransactionId xid)
> > {

Good point. I will add your comments.
--
Tatsuo Ishii

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2005-08-20 04:20:01 Re: Why is lock not released?
Previous Message Bruce Momjian 2005-08-19 21:49:15 Beta timing