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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: 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 04:29:50
Message-ID: 15214.1059020990@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> 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.

> Is the plan to allow one backend to shared lock the row while others can
> read it but not modify it, or is the idea to actually allow multiple
> backends to record their shared status on the row?

Plan? We have no plan to fix this :-(. But clearly there has to be
some way to tell which backends hold read locks on a shared-locked row,
else you can't tell if they've all dropped the lock or not.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Arguile 2003-07-24 04:30:51 Re: DBD::Pg, schema support
Previous Message Bruce Momjian 2003-07-24 04:12:27 Re: this is in plain text (row level locks)