BUG #15676: FOR UPDATE is not allowed with UNION ALL (and of course with UNION/INTERSECT/EXCEPT, DISTINCT?)
В списке pgsql-bugs по дате отправления:
| От | PG Bug reporting form |
|---|---|
| Тема | BUG #15676: FOR UPDATE is not allowed with UNION ALL (and of course with UNION/INTERSECT/EXCEPT, DISTINCT?) |
| Дата | |
| Msg-id | 15676-8248e6b0beac09c6@postgresql.org обсуждение исходный текст |
| Ответы |
Re: BUG #15676: FOR UPDATE is not allowed with UNION ALL (and of course with UNION/INTERSECT/EXCEPT, DISTINCT?)
|
| Список | pgsql-bugs |
The following bug has been logged on the website: Bug reference: 15676 Logged by: Gunther Schadow Email address: gunther.schadow@gmail.com PostgreSQL version: 11.2 Operating system: all Description: SELECT ... FOR UPDATE locks the roiw(s) being retrieved. UNION ALL is a nice way to retrieving rows from two tables, and implementation of UNION ALL is just a concatenation, each row returned comes from either one of the base table, and thus could be locked. Obviously the hard set semantics relational operators UNION (without ALL), INTERSECT, EXCEPT, and really also DISTINCT, should justifiable have limits in how you might to row locking. So it is justified not to support FOR UPDATE on those concepts. But on a UNION ALL it is not justified, only that it has not been done, and the error suggests that the UNION ALL case has not bee considered as fundamentally different from the other set operators.
В списке pgsql-bugs по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера