Re: Problems with PG 9.3 - Mailing list pgsql-admin

From Scott Marlowe
Subject Re: Problems with PG 9.3
Date
Msg-id CAOR=d=31qkmYbb-FTpOgGbMx=nDiPOxc3Os27uXxK7qWPnmf1g@mail.gmail.com
Whole thread Raw
In response to Re: Problems with PG 9.3  (Dhruv Shukla <dhruvshukla82@gmail.com>)
List pgsql-admin
On Tue, Aug 26, 2014 at 1:44 PM, Dhruv Shukla <dhruvshukla82@gmail.com> wrote:
> Here are all the changes
>
> max_connections               =1000 -> 200
> work_mem                        =4GB -> 1GB
> temp_mem                        =2GB -> 1GB
> shared_buffers                    =80GB -> 70GB
> maintenance_work_mem     = 16GB -> 2GB
> effective_cache_size           =130GB -> 180GB
> max_locks_per_transaction =64 -> 128
> autovacuum_max_workers   = 3 -> 12
> checkpoint_segments         = 64 -> 256

OK, so while this is happening, what's you memory look like on the db
box? Is it running low on memory? Or does it have plenty left over for
kernel cache? Is it releasing a lot of kernel cache to make room for
work_mem? You need to profile your server while this is happening.

vmstat
iostat
htop

are good tools to start with.

Are you running out of memory, CPU, or IO?


pgsql-admin by date:

Previous
From: Dhruv Shukla
Date:
Subject: Re: Problems with PG 9.3
Next
From: Peter Eisentraut
Date:
Subject: Re: pg_basebackup man-page confusion?