| From: | "MauMau" <maumau307(at)gmail(dot)com> |
|---|---|
| To: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgreSQL(dot)org> |
| Cc: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
| Subject: | Re: Auto-tuning work_mem and maintenance_work_mem |
| Date: | 2013-10-10 14:01:52 |
| Message-ID: | 6EF3C60AC46040C9A6CB178D8E13AD9C@maumau |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: "Bruce Momjian" <bruce(at)momjian(dot)us>
> I will work on auto-tuning temp_buffers next. Any other suggestions?
> wal_buffers is already auto-tuned.
Great work. I'm looking forward to becoming able to fully utilize system
resources right after initdb.
Although this is not directly related to memory, could you set
max_prepared_transactions = max_connections at initdb time? People must
feel frustrated when they can't run applications on a Java or .NET
application server and notice that they have to set
max_prepared_transactions and restart PostgreSQL. This is far from
friendly.
Regards
MauMau
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2013-10-10 14:24:26 | Re: Auto-tuning work_mem and maintenance_work_mem |
| Previous Message | Merlin Moncure | 2013-10-10 14:00:29 | Re: strange behavior of pg_trgm's similarity function |