Re: Workaround for working_mem max value in windows?

From: amul sul <sul_amul(at)yahoo(dot)co(dot)in>
To: Nick Eubank <nickeubank(at)gmail(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>, "Martin(dot)French(at)romaxtech(dot)com" <Martin(dot)French(at)romaxtech(dot)com>
Subject: Re: Workaround for working_mem max value in windows?
Date: 2014-04-17 07:05:43
Message-ID: 1397718343.88782.YahooMailNeo@web193504.mail.sg3.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Wednesday, 16 April 2014 10:05 PM, Nick Eubank <nickeubank(at)gmail(dot)com> wrote:

>Amul: thanks for the followup! Unfortunately, setting locally faces the same limitation 
>as setting things in the config file -- 
>I get an "ERROR: 3072000 is outside the valid range for parameter "work_mem" (64 .. 2097151)

>SQL state: 22023" problem if I set above ~1.9gb. :(

yes, you can set work_mem upto 2047MB.

Regards,
Amul Sul 

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Franck Routier 2014-04-17 15:11:25 Fast distinct not working as expected
Previous Message Nick Eubank 2014-04-17 01:35:37 Re: Workaround for working_mem max value in windows?