Re: [PERFORM] Workaround for working_mem max value in windows?

2014-04-16 Thread Nick Eubank
On Wednesday, April 16, 2014, Jeff Janes wrote: > On Tue, Apr 15, 2014 at 6:36 PM, Nick Eubank > > > wrote: > >> Hi all, >> >> A few years ago someone said postgres windows can't set working_mem above >> about 2 GB (www.postgresql.org/message-id/1789

Re: [PERFORM] Workaround for working_mem max value in windows?

2014-04-16 Thread Nick Eubank
On Wed, Apr 16, 2014 at 1:29 AM, amulsul 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: > h

[PERFORM] Workaround for working_mem max value in windows?

2014-04-15 Thread Nick Eubank
Hi all, A few years ago someone said postgres windows can't set working_mem above about 2 GB (www.postgresql.org/message-id/17895.1315869...@sss.pgh.pa.us -- seems to be same for maintenance_working_mem ). Im finding limit still present. I'm doing single user, single connection data intensive qu

[PERFORM] Tuning Postgres for Single connection use

2014-04-15 Thread Nick Eubank
> > > On Tuesday, April 15, 2014, Tom Lane wrote: > Jeff Janes writes: > > On Tue, Apr 15, 2014 at 9:12 AM, Nick Eubank > wrote: > >> Quick followup Jeff: it seems that I can't set work_mem above about 1gb > >> (can't get to 2gb. When I update c

Re: [PERFORM] Tuning Postgres for Single connection use

2014-04-15 Thread Nick Eubank
On Mon, Apr 14, 2014 at 5:19 PM, Jeff Janes wrote: > On Mon, Apr 14, 2014 at 2:46 PM, Nick Eubank wrote: > >> Any rules of thumb for work_mem, maintenance_work_mem, shared_buffer, >> etc. for a database that DOESN'T anticipate concurrent connections and that >&g

Re: [PERFORM] Tuning Postgres for Single connection use

2014-04-14 Thread Nick Eubank
Terrific -- thanks Gavin and Jeff! That's incredibly helpful for a n00b like me! On Mon, Apr 14, 2014 at 5:29 PM, Gavin Flower wrote: > In this list, please bottom post! > > I've added potentially useful advice below. > > > On 15/04/14 11:39, Nick Eubank wrote: &g

Re: [PERFORM] Tuning Postgres for Single connection use

2014-04-14 Thread Nick Eubank
Thanks Gavin -- would LOVE to. Sadly I'm in a weird situation where my hardware is not under my control, so I'm stuck making the best of what I have. Next time though! :) On Monday, April 14, 2014, Gavin Flower wrote: > On 15/04/14 09:46, Nick Eubank wrote: > > Any rules of

[PERFORM] Tuning Postgres for Single connection use

2014-04-14 Thread Nick Eubank
Any rules of thumb for work_mem, maintenance_work_mem, shared_buffer, etc. for a database that DOESN'T anticipate concurrent connections and that is doing lots of aggregate functions on large tables? All the advice I can find online on tuning (this