Re: this is in plain text (row level locks)

From: Mike Mascari <mascarm(at)mascari(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, sailesh(at)cs(dot)berkeley(dot)edu, Jenny - <nat_lazy(at)hotmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: this is in plain text (row level locks)
Date: 2003-07-24 03:38:54
Message-ID: 3F1F54CE.70203@mascari.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>
>>Sailesh Krishnamurthy wrote:
>>
>>>Does pgsql only record X locks on the individual tuples on-disk or
>>>does it do so for S locks as well ?
>
>
>>We don't need to shared lock individual rows because of MVCC --- well,
>>we sort of do by recording our xid in our proc structure, so folks don't
>>change things underneath us. We prevent expired rows from disappearing
>>from the disk by others looking at our proc start xid.
>
>
> This is actually an issue though. Row-level shared locks would be
> really nice to have for foreign-key handling. Right now we have to
> use X locks for those, and that leads to deadlocking problems for
> applications.

Yes! Yes! It's the last big hurdle for an otherwise excellent RI
implementation...

Just wanted "Joe-user's" enthusiasm for row-level S locks registered
somewhere... :-)

Mike Mascari
mascarm(at)mascari(dot)com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-07-24 04:08:07 Re: [HACKERS] PATCH: Memory leaks on start-up
Previous Message Bruce Momjian 2003-07-24 02:26:43 Re: [HACKERS] clock_timestamp() and transcation_timestamp() patch