Re: Auto-tuning work_mem and maintenance_work_mem
| От | Dimitri Fontaine |
|---|---|
| Тема | Re: Auto-tuning work_mem and maintenance_work_mem |
| Дата | |
| Msg-id | m28uxx53mt.fsf@2ndQuadrant.fr обсуждение исходный текст |
| Ответ на | Re: Auto-tuning work_mem and maintenance_work_mem ("MauMau" <maumau307@gmail.com>) |
| Ответы |
Re: Auto-tuning work_mem and maintenance_work_mem
|
| Список | pgsql-hackers |
"MauMau" <maumau307@gmail.com> writes: > I understand this problem occurs only when the user configured the > application server to use distributed transactions, the application server > crashed between prepare and commit/rollback, and the user doesn't recover > the application server. So only improper operation produces the problem. The reason why that parameter default has changed from 5 to 0 is that some people would mistakenly use a prepared transaction without a transaction manager. Few only people are actually using a transaction manager that it's better to have them have to set PostgreSQL. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
В списке pgsql-hackers по дате отправления: