| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | MauMau <maumau307(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com> |
| Subject: | Re: Auto-tuning work_mem and maintenance_work_mem |
| Date: | 2013-10-15 12:42:45 |
| Message-ID: | 20131015124245.GA8001@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-10-15 21:41:18 +0900, MauMau wrote:
> Likewise, non-zero max_prepared_transactons would improve the
> impression of PostgreSQL (for limited number of users, though), and it
> wouldn't do any harm.
I've seen several sites shutting down because of forgotten prepared
transactions causing bloat and anti-wraparound shutdowns.
A big, big -1 for changing that default.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MauMau | 2013-10-15 12:47:55 | Re: Auto-tuning work_mem and maintenance_work_mem |
| Previous Message | Robert Haas | 2013-10-15 12:42:20 | Re: logical changeset generation v6.2 |