From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Vadim Mikheev <vadim(at)krs(dot)ru> |
Cc: | PostgreSQL Developers List <hackers(at)postgreSQL(dot)org>, dz(at)cs(dot)unitn(dot)it |
Subject: | Re: [HACKERS] XIDTAG ??? |
Date: | 1999-05-03 16:27:28 |
Message-ID: | 199905031627.MAA21498@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Why both
>
> int pid;
> TransactionId xid;
>
> are used in XIDTAG?
>
> lock.c:
> * normal lock user lock
> *
> * lockmethod 1 2
> * tag.relId rel oid 0
> ^^^^^^^^^^^^^^^^^
> Due to this, user-lock LOCKTAG is always different from
> normal-lock tag and so XIDTAG.lock is different also.
>
> * tag.ItemPointerData.ip_blkid block id lock id2
> * tag.ItemPointerData.ip_posid tuple offset lock id1
> * xid.pid 0 backend pid
> * xid.xid xid or 0 0
>
> Why not get rid of XIDTAG.xid and use XIDTAG.pid equal
> to backend pid for both lock methods?
Probably no reason for the transaction id. I don't remember that being
used at all.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Ross J. Reedstrom | 1999-05-03 17:01:31 | pg_dump bug (was Re: [SQL] Slow Inserts Again) |
Previous Message | Vadim Mikheev | 1999-05-03 16:18:00 | XIDTAG ??? |