From: Josh Berkus <josh@agliodbs.com>
To: Justin Long <justinlong@strategicnetwork.org>
To: pgsql-performance@postgresql.org
Subject: Re: Optimization
Date: Mon, 28 Jul 2003 12:27:44 -0700
Message-ID: <200307281227.44072.josh@agliodbs.com> (raw)
In-Reply-To: <000f01c35523$f13dee90$ecd36044@tarzan>
References: <000f01c35523$f13dee90$ecd36044@tarzan>
Justin,
> I am trying to understand the various factors used by Postgres to optimize.
I presently have a dual-866 Dell server with 1GB of memory. I've done the
following:
see: http://www.varlena.com/varlena/GeneralBits/Tidbits/index.php
which has articles on .conf files.
(feel free to link these articles at PHPbuilder.com and elsewhere!)
> The databases I'm using have about 200,000+ news headlines with full-text
indexes (which range upwards of a few million records). They are updated
about every 5 to 10 minutes, which means I also have to run a vacuum about
once every 2 to 3 hours at least. As I get more updates obviously the
efficiency goes down. I'm trying to make the most of this system but don't
fully understand PG's optimization stuff.
Unless you're running PostgreSQL 7.1 or earlier, you should be VACUUMing every
10-15 minutes, not every 2-3 hours. Regular VACUUM does not lock your
database. You will also want to increase your FSM_relations so that VACUUM
is more effective/efficient; again, see the articles.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, justinlong@strategicnetwork.org
Subject: Re: Optimization
In-Reply-To: <200307281227.44072.josh@agliodbs.com>
* 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