| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Roland Turner <raz(dot)cbfgterfdy(dot)bet(at)raz(dot)cx> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Lock contention, docs vs. reality |
| Date: | 2007-04-23 04:45:12 |
| Message-ID: | 14289.1177303512@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Roland Turner <raz(dot)cbfgterfdy(dot)bet(at)raz(dot)cx> writes:
> I'm working with 7.4, but the 8.2 docs[1] have the same apparent error:
> ROW SHARE
> Conflicts with the EXCLUSIVE and ACCESS EXCLUSIVE lock modes.
> If that conflict list were correct, then ROW SHARE wouldn't conflict
> with itself, much less with ROW EXCLUSIVE (required to prevent
> INSERT/UPDATE/DELETE); commonsense dictates that it should conflict with
> both, and experiment demonstrates that it actually does so.
A moment's examination of the source code (see the conflict tables in
src/backend/storage/lmgr/lock.c) shows that the documentation claim is
correct. Please provide your experiment to the contrary.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mageshwaran | 2007-04-23 05:21:31 | Postgresql Help |
| Previous Message | Tom Lane | 2007-04-23 04:31:32 | Re: can't start tsearch2 in 8.2.4 |