Re: Fwd: Regarding change in the size of database

On Thu, Oct 27, 2016 at 4:53 PM, harish Reddy <harishr536@gmail.com> wrote:

Hi Sir, 

Thank you for you feedback my postgres is running on 9.1 version and when i checked  that autovacuum in  my production by command ps -axww | grep autovacuum it says the output as it has some process running with this id so how to solve my problem but in postgress config file it was commented.

My application is an online ERP which is supported by openbravo has an users of about 150(arount 50 active users) with it and could you suggest me the perfect variables to set us in postgres config file. 

The system has a RAM of 16 GB and the following variables 

Variable	Setting value
max_connections	200
shared_buffers	4096MB
work_mem	24MB
maintenance_work_mem	512MB
effective_cache_size	4096MB

 

On Thu, Oct 27, 2016 at 9:04 AM, Jayadevan M <maymala.jayadevan@gmail.com> wrote:

On Wed, Oct 26, 2016 at 9:51 PM, harish Reddy <harishr536@gmail.com> wrote:

Hi Jayadevan,

Firstly Thank you so much for your valuable information provided, So what should i do for increasing my database performance? and could you suggest me how to continue to the vacuum process and will it decrease my database performance?

 

Please read this article

https://wiki.postgresql.org/wiki/Guide_to_reporting_problems

i.e - "Mention your database version", "A description of what you are trying to achieve and what results you expect" etc etc.

And this.

https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server

 

Do you have autovacuum working? 

https://www.postgresql.org/docs/current/static/runtime-config-autovacuum.html

 

Try installing pgbouncer for connection pooling if you need 200 active connections. You can check for active connections using answers on this page: http://serverfault.com/questions/128284/how-to-see-active-connections-and-current-activity-in-postgresql-8-4

Another suggestion that might come your way is to upgrade your postgres version as 9.1 has recently been made EOL. 

"explain analyze" can be used to debug slow queries. See this page for more info: https://www.postgresql.org/docs/9.1/static/sql-explain.html

If you need further help, you will have to be more specific on what performance problems you are facing, with their explain anaylze output for folks here to help you out.

Amitabh