From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | clark(dot)evans(at)manhattanproject(dot)com (Clark Evans) |
Cc: | vadim(at)krs(dot)ru, hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] FOR SHARE LOCK clause ? |
Date: | 1999-01-06 07:43:48 |
Message-ID: | 199901060743.CAA28893@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> In any case, I'm not really sure what this locking
> in share mode would get you... could you explain
> in the context of the above examples.
I will take a stab at it.
Locking in shared mode would cause any row read by the SELECT to be
remain unmodified until its transaction completes. Other SELECTs can
read it, but writer have to wait and can not modify it.
--
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 | Billy G. Allie | 1999-01-06 08:18:12 | Re: Stale porting list? |
Previous Message | Clark Evans | 1999-01-06 07:24:27 | Re: [HACKERS] FOR SHARE LOCK clause ? |