Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: High update activity, PostgreSQL vs BigDBMS


  • From: "Joshua D. Drake" <jd(at)commandprompt(dot)com>
  • To: Guy Rouillier <guyr-ml1(at)burntmail(dot)com>
  • Cc: PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>
  • Subject: Re: High update activity, PostgreSQL vs BigDBMS
  • Date: Sat, 06 Jan 2007 20:56:47 -0800
  • Message-id: <1168145807(dot)869(dot)22(dot)camel(at)localhost(dot)localdomain>

> 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






Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group