From: | Barbara Stephenson <barbara(at)turbocorp(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | tuning our database by increasing shared buffer |
Date: | 2009-06-23 19:02:30 |
Message-ID: | 200906231502.30337.barbara@turbocorp.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello,
We will be consolidating from 4 databases to 2 and want to make sure that
these parameters are the only ones that need changing. Please advise.
Current Future
===== =====
Max_connection = 50 125
Shared_buffers = 16MB 48MB
My concern is that max_locks_per_transaction and max_prepared_transaction are
still set as default??
Shouldn't we increase the max_locks_per_transaction from 64 to 100 or 128
since we have more than doubled the # of connections?
max_prepared_transaction is set at default of 5 which is says if we use it to
set it to max_connection.
Or leaving those 2 max parameters as default would be ok?
--
Regards,
Barbara Stephenson
EDI Specialist/Programmer
Turbo, division of OHL
2251 Jesse Jewell Pkwy
Gainesville, GA 30507
tel: (678)989-3020 fax: (404)935-6171
barbara(at)turbocorp(dot)com
www.ohl.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-06-23 19:25:51 | Re: tuning our database by increasing shared buffer |
Previous Message | Tom Lane | 2009-06-23 13:29:51 | Re: [HACKERS] PK not being restored |