running transactions in postgresql

Started by Jenny -over 22 years ago2 messages
#1Jenny -
nat_lazy@hotmail.com

<html><div style='background-color:'><DIV>hi,</DIV>
<DIV>&nbsp;Iam working on project that deals with analyzing the locking mechanism in postgresql. </DIV>
<DIV>I started a transaction in postgresql with 'begin work;' and noticed that even though no locks have been taken yet, there still exists data in LockData datastructures that indicates that the transaction i just started running is waiting for a lock.Does anyone know why this happens? I f not , could someone guide me to the appropriate site or mailinglist where my question can be answered.</DIV>
<DIV>thank you</DIV>
<DIV>Jenny</DIV></div><br clear=all><hr>Protect your PC - <a href="http://g.msn.com/8HMEENUS/2755??PS=&quot;&gt;Click here</a> for McAfee.com VirusScan Online </html>

#2Alvaro Herrera
alvherre@dcc.uchile.cl
In reply to: Jenny - (#1)
Re: running transactions in postgresql

On Tue, Jul 08, 2003 at 07:41:48AM -0700, Jenny - wrote:

[unquotable HTML, please post only text/plain!]

At transaction start
(src/backend/access/transam/xact.c::StartTransaction()),
src/backend/storage/lmgr/lmgr.c::XactLockTableInsert() is executed,
which takes a special lock on a ficticious XactLockTableId.

Maybe that's what you are seeing?

--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Uno puede defenderse de los ataques; contra los elogios se esta indefenso"