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 archives
  Advanced Search

Re: dbt-2 tuning results with postgresql-8.3.5


  • From: Greg Smith <gsmith(at)gregsmith(dot)com>
  • To: Mark Wong <markwkm(at)gmail(dot)com>
  • Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>, Selena Deckelmann <selenamarie(at)gmail(dot)com>, Gabrielle Roth <gorthx(at)gmail(dot)com>
  • Subject: Re: dbt-2 tuning results with postgresql-8.3.5
  • Date: Mon, 22 Dec 2008 22:51:08 -0500 (EST)
  • Message-id: <Pine.GSO.4.64.0812222236220.6114@westnet.com> <text/plain>

On Mon, 22 Dec 2008, Mark Wong wrote:

The shared_buffers are the default, 24MB.  The database parameters are
saved, probably unclearly, here's an example link:

http://207.173.203.223/~markwkm/community6/dbt2/baseline.1000.1/db/param.out

That's a bit painful to slog through to find what was changed from the defaults. How about saving the output from this query instead, or in addition to the version sorted by name:

select name,setting,source,short_desc from pg_settings order by source,name;

Makes it easier to ignore everything that isn't set.

I should probably run your pgtune script, huh?

That's basically where the suggestions for center points I made came from. The only other thing that does that might be interesting to examine is that it bumps up checkpoint_completion_target to 0.9 once you've got a large number of checkpoint_segments.

--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group