| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Shared row locking |
| Date: | 2004-12-17 02:09:26 |
| Message-ID: | 41C23FD6.2030405@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> The SQL spec does not say anything on this respect (that I can find).
> It only talks of "FOR UPDATE" and "FOR READ ONLY". However, because the
> FK code uses SPI to do the locking, we definitely have to expose the
> funcionality through SQL. So I think we need a new clause, which I
> propose to be "FOR SHARE".
MySQL uses LOCK IN SHARE MODE:
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-12-17 02:17:43 | Re: [INTERFACES] PL/Python: How do I use result methods? |
| Previous Message | Bruce Momjian | 2004-12-17 01:57:51 | Re: Shared row locking |