Postgres Pro
Downloads
Home   >   mailing lists

Re: Workaround for working_mem max value in windows? - Mailing list pgsql-performance

From Nick Eubank
Subject Re: Workaround for working_mem max value in windows?
Date
Msg-id CAFWQgOnN_KL+i3jpW9BSR8zWnXys09awJ90GH5Td753Nb-NNRQ@mail.gmail.com
Whole thread Raw
In response to Re: Workaround for working_mem max value in windows?  (amulsul <sul_amul@yahoo.co.in>)
Responses Re: Workaround for working_mem max value in windows?
Re: Workaround for working_mem max value in windows?
List pgsql-performance
Tree view



On Wed, Apr 16, 2014 at 1:29 AM, amulsul <sul_amul@yahoo.co.in> wrote:
>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

Thanks all!

Sorry Martin, should have been clearer on my usage plans: I'm only interested in optimizing for single-connection, sequential high-demand queries, so I think I'm safe bumping up memory usage, even if it's usually a disastrous idea for most users.  I'll definitely check with the Enterprise folks!

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

pgsql-performance by date:

Previous
From: Linos
Date:
Subject: Re: unneeded joins on view
Next
From: "Martin French"
Date:
Subject: Re: Workaround for working_mem max value in windows?