From: | TonyS <tony(at)exquisiteimages(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Would like to know how analyze works technically |
Date: | 2015-04-01 17:47:32 |
Message-ID: | 8bb916e3e7b9fa1e4533a8b11c7ca2c1.squirrel@www.exquisiteimages.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, April 1, 2015 12:30 pm, Igor Neyman [via PostgreSQL] wrote:
>>
>> TonyS <[hidden email]</user/SendEmail.jtp?type=node&node=5844292&i=0>>
>> wrote:
>>
>>
>
> name,current_setting,source autovacuum,off,configuration file
> synchronous_commit,off,configuration file TimeZone,localtime,configuration
> file unix_socket_directories,/var/run/postgresql,configuration file
> wal_buffers,8MB,configuration file work_mem,1536MB,configuration file
>
>
> ---
>
>
> ? work_mem,1536MB,configuration file
>
>
>
> IIRC, your RAM is 8GB. Your work_mem is too high. Actual memory used
> for sorting, etc... could be multiples of work_mem setting.
>
> That could be the reason for your memory problems. I'd suggest to set it
> to 16MB, and see if you can avoid "on disk" sorting. If not - gradually
> increase work_mem.
>
> Regards,
>
>
> Igor Neyman
>
Thanks Igor,
I will try changing that. I pretty much just let pgtune set all of those
values for me.
--
View this message in context: http://postgresql.nabble.com/Would-like-to-know-how-analyze-works-technically-tp5844197p5844318.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | James Cloos | 2015-04-01 18:50:21 | now() vs 'epoch'::timestamp |
Previous Message | FarjadFarid(ChkNet) | 2015-04-01 16:41:57 | Re: Would like to know how analyze works technically |