pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Guy Rouillier <guyr-ml1@burntmail.com>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: High update activity, PostgreSQL vs BigDBMS
Date: Sat, 06 Jan 2007 20:56:47 -0800
Message-ID: <1168145807.869.22.camel@localhost.localdomain> (raw)
In-Reply-To: <45A077FB.3010802@burntmail.com>
References: <45935A49.6080602@burntmail.com>
	<bf54be870612280106n1247520dtb48e10cb4bdc43e9@mail.gmail.com>
	<459F0EA6.30403@burntmail.com>
	<BB4FC28F-BDC1-424F-B330-EE9204404F1A@fastcrypt.com>
	<45A077FB.3010802@burntmail.com>


> Regarding shared_buffers=750MB, the last discussions I remember on this 
> subject said that anything over 10,000 (8K buffers = 80 MB) had unproven 
> benefits.  So I'm surprised to see such a large value suggested.  I'll 
> certainly give it a try and see what happens.
> 

That is old news :) As of 8.1 it is quite beneficial to go well above
the aforementioned amount.

J


> >>
> >> autovacuum=on
> >> stats_row_level = on
> >> max_connections = 10
> >> listen_addresses = 'db01,localhost'
> >> shared_buffers = 128MB
> >> work_mem = 16MB
> >> maintenance_work_mem = 64MB
> >> temp_buffers = 32MB
> >> max_fsm_pages = 204800
> >> checkpoint_segments = 30
> >> redirect_stderr = on
> >> log_line_prefix = '%t %d'
-- 

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate






view thread (39+ messages)  latest in thread

Message-ID: <1168145807.869.22.camel@localhost.localdomain>
Permalink:  ../1168145807.869.22.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1168145807.869.22.camel@localhost.localdomain

 · 

reply

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: jd@commandprompt.com, guyr-ml1@burntmail.com
  Subject: Re: High update activity, PostgreSQL vs BigDBMS
  In-Reply-To: <1168145807.869.22.camel@localhost.localdomain>

* 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