Re: Auto-tuning work_mem and maintenance_work_mem - Mailing list pgsql-hackers

From MauMau
Subject Re: Auto-tuning work_mem and maintenance_work_mem
Date
Msg-id 6EF3C60AC46040C9A6CB178D8E13AD9C@maumau
Whole thread Raw
In response to Auto-tuning work_mem and maintenance_work_mem  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Auto-tuning work_mem and maintenance_work_mem  (Bruce Momjian <bruce@momjian.us>)
Re: Auto-tuning work_mem and maintenance_work_mem  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
From: "Bruce Momjian" <bruce@momjian.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






pgsql-hackers by date:

Previous
From: Mike Blackwell
Date:
Subject: Re: Patch for reserved connections for replication users
Next
From: Merlin Moncure
Date:
Subject: Re: strange behavior of pg_trgm's similarity function