Re: Surprising behaviour of \set AUTOCOMMIT ON
| От | David G. Johnston |
|---|---|
| Тема | Re: Surprising behaviour of \set AUTOCOMMIT ON |
| Дата | |
| Msg-id | CAKFQuwbb1edcD6RYb=o1dNfNLqwdLDin09DPFB3xEtdUuqBx-Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Surprising behaviour of \set AUTOCOMMIT ON (Venkata Balaji N <nag1010@gmail.com>) |
| Ответы |
Re: Surprising behaviour of \set AUTOCOMMIT ON
|
| Список | pgsql-hackers |
[...]committing all the previously open transactions[...]
"All"? There can only ever be at most one open transaction at any given time...
I don't have a fundamental issue with saying "when turning auto-commit on you are also requesting that the open transaction, if there is one, is committed immediately." I'm more inclined to think an error is the correct solution - or to respond in a way conditional to the present usage (interactive vs. script). I disagree with Robert's unsubstantiated belief regarding ON_ERROR_STOP and think that it captures the relevant user-intent for this behavior as well.
David J.
В списке pgsql-hackers по дате отправления: