| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | diemersebastien(at)yahoo(dot)fr, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Missing lock conflict for ROW SHARE |
| Date: | 2017-04-21 19:39:48 |
| Message-ID: | eb963b35-367d-2694-118f-383b323a90d6@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 4/12/17 06:00, diemersebastien(at)yahoo(dot)fr wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.4/static/explicit-locking.html
> Description:
>
> In my experience ROW SHARE conflicts with ROW EXCLUSIVE and this is not
> mentioned in the documentation. Am I missing something ?
This is not correct. See the source for how the lock conflicts are
defined:
<https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/backend/storage/lmgr/lock.c;h=3e33bc104d3ee71ec87efb0c39485dda4867c00c;hb=c7681b2b9a115eb05048a485480826bc0efa6d3b#l62>
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-04-21 23:49:37 | Re: Small patch for the section "rules-views" |
| Previous Message | Peter Eisentraut | 2017-04-21 19:33:50 | Re: There is one "a" too much |