Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-performance-owner+M51531=pgsql-performance-ar@postgresql.org>)
 id 1WaLDz-0003vi-Hp
 for pgsql-performance@arkaria.postgresql.org; Wed, 16 Apr 2014 08:29:43 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-performance-owner+M51531=pgsql-performance-ar@postgresql.org>)
 id 1WaLDy-0001tM-Qs
 for pgsql-performance@arkaria.postgresql.org; Wed, 16 Apr 2014 08:29:42 +0000
Received: from makus.postgresql.org ([2001:4800:7903:4::125])
 by malur.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <sul_amul@yahoo.co.in>) id 1WaLDx-0001tF-Kj
 for pgsql-performance@postgresql.org; Wed, 16 Apr 2014 08:29:41 +0000
Received: from sam.nabble.com ([216.139.236.26])
 by makus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <sul_amul@yahoo.co.in>) id 1WaLDv-0007Hz-Ks
 for pgsql-performance@postgresql.org; Wed, 16 Apr 2014 08:29:40 +0000
Received: from [192.168.236.26] (helo=sam.nabble.com)
 by sam.nabble.com with esmtp (Exim 4.72)
 (envelope-from <sul_amul@yahoo.co.in>) id 1WaLDv-00040Z-B3
 for pgsql-performance@postgresql.org; Wed, 16 Apr 2014 01:29:39 -0700
Date: Wed, 16 Apr 2014 01:29:39 -0700 (PDT)
From: amulsul <sul_amul@yahoo.co.in>
To: pgsql-performance@postgresql.org
Message-ID: <1397636979325-5800216.post@n5.nabble.com>
In-Reply-To: 
 <CAFWQgO=fgsniCMvNiReVdcBc9+hB6N0b8SFVCY9xOjQpP=GSmQ@mail.gmail.com>
References: 
 <CAFWQgO=fgsniCMvNiReVdcBc9+hB6N0b8SFVCY9xOjQpP=GSmQ@mail.gmail.com>
Subject: Re: Workaround for working_mem max value in windows?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: 2.8 (++)
List-Archive: <http://archives.postgresql.org/pgsql-performance>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-performance.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@postgresql.org>
List-Post: <mailto:pgsql-performance@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-performance>
List-Unsubscribe: 
 <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
X-Mailing-List: pgsql-performance
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

>Anyone found a work around?

Wouldn't it helpful, setting it in your session?

set work_mem='2000MB';
set maintenance_work_mem='2000MB';

do rest of sql after ..... 

Regards,
Amul Sul



--
View this message in context: http://postgresql.1045698.n5.nabble.com/Workaround-for-working-mem-max-value-in-windows-tp5800170p5800216.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance