Re: [PATCHES] NO WAIT ...
| От | Rod Taylor |
|---|---|
| Тема | Re: [PATCHES] NO WAIT ... |
| Дата | |
| Msg-id | 1077206712.25444.44.camel@jester обсуждение исходный текст |
| Ответ на | Re: [PATCHES] NO WAIT ... ("Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>) |
| Список | pgsql-hackers |
> I vote for the GUC. Imho it is not comparable to the "autocommit" case, > since it does not change the way your appl needs to react (appl needs to > react to deadlock already). Wrote one program a while ago that was very time sensitive. By the time deadlock detection had been kicked off, the data was already invalid and due to be replaced -- thus, it's impossible to have deadlocks with the chosen design for that application. The point is, PostgreSQL is fairly versatile and is a component of many different environments. Method X might be great for what you're doing, but it doesn't apply across the board. The regex GUC doesn't impact a majority of applications either, but it proved catastrophic to some.
В списке pgsql-hackers по дате отправления: