Re: [BUGS] Status of issue 4593
От | Gregory Stark |
---|---|
Тема | Re: [BUGS] Status of issue 4593 |
Дата | |
Msg-id | 871vv7hw0q.fsf@oxford.xeocode.com обсуждение исходный текст |
Ответ на | Re: [BUGS] Status of issue 4593 ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
Ответы |
Re: [BUGS] Status of issue 4593
|
Список | pgsql-hackers |
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes: >>>> Josh Berkus <josh@agliodbs.com> wrote: >> we'd break 100,000 existing Java applications if we changed the > error. > > In what way would an application want to treat deadlocks and update > conflicts differently? Both result from conflicts with concurrent > transactions and can be retried automatically. It seems like an > implementation detail with little chance of impact on applications to > me. Can anyone provide a contrary example or argument? Well generally deadlocks are treated differently in that they are treated by rewriting the application to not cause deadlocks. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB'sPostgreSQL training!
В списке pgsql-hackers по дате отправления: