Re: Would like to know how analyze works technically

From: Bill Moran <wmoran(at)potentialtech(dot)com>
To: TonyS <tony(at)exquisiteimages(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Would like to know how analyze works technically
Date: 2015-04-01 19:36:09
Message-ID: 20150401153609.dab8d65b4c25d42af14c62ae@potentialtech.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 1 Apr 2015 10:47:32 -0700 (MST)
TonyS <tony(at)exquisiteimages(dot)com> wrote:

> 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.

If pgtune set 1.5G of work_mem, then someone should file a bug report.

--
Bill Moran

In response to

Browse pgsql-general by date

  From Date Subject
Next Message TonyS 2015-04-01 19:51:06 Re: Would like to know how analyze works technically
Previous Message Tom Lane 2015-04-01 19:17:59 Re: now() vs 'epoch'::timestamp