| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | MauMau <maumau307(at)gmail(dot)com> |
| Cc: | 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-10 14:49:40 |
| Message-ID: | 20131010144940.GL7092@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 10, 2013 at 11:01:52PM +0900, MauMau wrote:
> 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.
I think the problem is that many users don't need prepared transactions
and therefore don't want the overhead. Is that still accurate?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-10-10 14:51:17 | Re: [COMMITTERS] pgsql: Revive line type |
| Previous Message | MauMau | 2013-10-10 14:44:39 | Re: Auto-tuning work_mem and maintenance_work_mem |