| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | "MauMau" <maumau307(at)gmail(dot)com> |
| Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgreSQL(dot)org>, "Josh Berkus" <josh(at)agliodbs(dot)com> |
| Subject: | Re: Auto-tuning work_mem and maintenance_work_mem |
| Date: | 2013-10-13 20:15:22 |
| Message-ID: | m28uxx53mt.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"MauMau" <maumau307(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2013-10-13 20:18:37 | Re: Auto-tuning work_mem and maintenance_work_mem |
| Previous Message | Andres Freund | 2013-10-13 20:10:54 | Re: removing old ports and architectures |