On Thu, Oct 10, 2013 at 11:01:52PM +0900, MauMau wrote: > From: "Bruce Momjian" <br...@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.
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 <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
