Re: Transaction in plpgslq
От | Rafa Couto |
---|---|
Тема | Re: Transaction in plpgslq |
Дата | |
Msg-id | 22df564b050524034045f8c174@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Transaction in plpgslq (Andrew Hammond <ahammond@ca.afilias.info>) |
Ответы |
Re: Transaction in plpgslq
Re: Transaction in plpgslq |
Список | pgsql-sql |
2005/5/20, Andrew Hammond <ahammond@ca.afilias.info>: > The solution to your problem is locking (or concurrency control if you > prefer). While we're at it, we might as well optimize your statement a > little too using ORDER BY with LIMIT instead of min(). > > SELECT id INTO _contacto_id > FROM contactos > WHERE contactos.operadora_id IS NULL > AND contactos.actividad_id > = _actividad_id > ORDER BY id LIMIT 1 > FOR UPDATE; > > Take a look at the "FOR UPDATE" section of the SELECT description for an > explanation of how this works. I understand "FOR UPDATE" clause is locking while is selecting rows only. It does not secure atomic execution from 'SELECT' to 'UPDATE' in next statement. Is not it? -- Rafa Couto (caligari)
В списке pgsql-sql по дате отправления: