Re: Correction in SHARE ROW EXCLUSIVE lock description

From: Euler Taveira <euler(at)timbira(dot)com(dot)br>
To: diemersebastien(at)yahoo(dot)fr
Cc: pgsql-docs(at)postgresql(dot)org
Subject: Re: Correction in SHARE ROW EXCLUSIVE lock description
Date: 2017-10-10 15:55:37
Message-ID: CAHE3wgiPZv5pto9cFwaHUS2XJdRCX17RNuGNZDu064JrUKD6PQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

2017-10-09 6:07 GMT-03:00 <diemersebastien(at)yahoo(dot)fr>:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.4/static/explicit-locking.html
> Description:
>
> The documentation says :
>
> &quot;This lock mode is not automatically acquired by any PostgreSQL command.&quot;
>
You are reading 9.4 documentation but...

> I am wrong if I say that a &quot;ADD CONSTRAINT toto FOREIGN KEY&quot; command will
> take a SHARE ROW EXCLUSIVE lock on both tables concerned by the foreign key
> ?
>
... you are testing with >= 9.5. Indeed, SREL replaced AEL in this
ALTER TABLE case [1].

[1] https://www.postgresql.org/docs/9.5/static/explicit-locking.html

--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Magnus Hagander 2017-10-11 08:11:23 Re: Typo at https://www.postgresql.org/about/featurematrix/detail/292/
Previous Message David G. Johnston 2017-10-10 14:46:44 Re: 19.2. File Locations doesn't tell you the file locations!