On Mon, Apr 14, 2014 at 5:19 PM, Jeff Janes jeff.ja...@gmail.com wrote:
On Mon, Apr 14, 2014 at 2:46 PM, Nick Eubank nickeub...@gmail.com 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
On Tue, Apr 15, 2014 at 9:12 AM, Nick Eubank nickeub...@gmail.com wrote:
On Mon, Apr 14, 2014 at 5:19 PM, Jeff Janes jeff.ja...@gmail.com wrote:
I'd go with a small shared_buffers, like 128MB, and let the OS cache as
much as possible. This minimizes the amount of double buffering.
And set
From: pgsql-performance-ow...@postgresql.org
[mailto:pgsql-performance-ow...@postgresql.org] On Behalf Of Nick Eubank
Sent: Tuesday, April 15, 2014 11:12 AM
To: Jeff Janes
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Tuning Postgres for Single connection use
On Mon, Apr 14
Jeff Janes jeff.ja...@gmail.com writes:
On Tue, Apr 15, 2014 at 9:12 AM, Nick Eubank nickeub...@gmail.com wrote:
Quick followup Jeff: it seems that I can't set work_mem above about 1gb
(can't get to 2gb. When I update config, the values just don't change in
SHOW ALL -- integer constraint?). Is
On Tuesday, April 15, 2014, Tom Lane t...@sss.pgh.pa.us wrote:
Jeff Janes jeff.ja...@gmail.com writes:
On Tue, Apr 15, 2014 at 9:12 AM, Nick Eubank nickeub...@gmail.com
wrote:
Quick followup Jeff: it seems that I can't set work_mem above about 1gb
(can't get to 2gb. When I update
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
On 15/04/14 09:46, 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 is doing lots of aggregate functions
on large tables? All the advice I can find online on tuning (this
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 gavinflo...@archidevsys.co.nz
wrote:
On 15/04/14 09:46, Nick Eubank wrote:
Any
On 04/14/2014 05: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 is doing lots of aggregate functions
on large tables? All the advice I can find online on tuning
On Mon, Apr 14, 2014 at 2:46 PM, Nick Eubank nickeub...@gmail.com 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
is doing lots of aggregate functions on large tables? All the advice I
can
In this list, please bottom post!
I've added potentially useful advice below.
On 15/04/14 11:39, Nick Eubank wrote:
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
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 gavinflo...@archidevsys.co.nz
wrote:
In this list, please bottom post!
I've added potentially useful advice below.
On 15/04/14 11:39, Nick Eubank wrote:
12 matches
Mail list logo
