| From: | Lawrence Wetsel <trey_wetsel(at)mac(dot)com> |
|---|---|
| To: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Initial performance tuning question |
| Date: | 2016-03-15 19:43:43 |
| Message-ID: | f7377584-8fa5-4da2-a861-ed2fb97b929d@me.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Hello,
I am setting up a PostgreSQL instance in the cloud for a customer and a couple of months ago I couldn't spell PostgreSQL.
I have a few questions:
What should I look for in the way of performance tuning/how should I set it up? RHEL and CentOS will be used. RAM...probably between 3-4G. I'm not sure about the storage type. As for what I'm tuning...I'm more interested in response times than transactions per second. Could I create a script to automate the performance tuning?
Also. I'm looking at Tenable's PostgreSQL 9.1 Best Practices DB and PostgreSQL 9.1 Best Practices Unix OS, what should I look for in the way of hardening/how should I set it up?
Thank you for any help and/or suggestions!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-03-15 19:49:25 | Re: [NOVICE] WHERE clause not used when index is used |
| Previous Message | Lawrence Wetsel | 2016-03-15 19:34:48 | Initial audit question |