From: amul sul <sul_amul@yahoo.co.in>
To: Nick Eubank <nickeubank@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Cc: Martin.French@romaxtech.com <Martin.French@romaxtech.com>
Subject: Re: Workaround for working_mem max value in windows?
Date: Thu, 17 Apr 2014 15:05:43 +0800 (SGT)
Message-ID: <1397718343.88782.YahooMailNeo@web193504.mail.sg3.yahoo.com> (raw)
In-Reply-To: <CAFWQgOnN_KL+i3jpW9BSR8zWnXys09awJ90GH5Td753Nb-NNRQ@mail.gmail.com>
References: <CAFWQgO=fgsniCMvNiReVdcBc9+hB6N0b8SFVCY9xOjQpP=GSmQ@mail.gmail.com>
<1397636979325-5800216.post@n5.nabble.com>
<CAFWQgOnN_KL+i3jpW9BSR8zWnXys09awJ90GH5Td753Nb-NNRQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On Wednesday, 16 April 2014 10:05 PM, Nick Eubank <nickeubank@gmail.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
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sul_amul@yahoo.co.in, nickeubank@gmail.com, Martin.French@romaxtech.com
Subject: Re: Workaround for working_mem max value in windows?
In-Reply-To: <1397718343.88782.YahooMailNeo@web193504.mail.sg3.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox