From: Josh Berkus <josh@agliodbs.com>
To: Wager, Ryan D [NTK] <Ryan.D.Wager@mail.sprint.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: query rewrite using materialized views
Date: Tue, 4 Jan 2005 11:16:49 -0800
Message-ID: <200501041116.49197.josh@agliodbs.com> (raw)
In-Reply-To: <8543375597A43D4D8388D75ACD32B9B301F72C19@PDAWB06C.ad.sprint.com>
References: <8543375597A43D4D8388D75ACD32B9B301F72C19@PDAWB06C.ad.sprint.com>
Wagner,
> If there is anyone that can give me some tweak parameters or design
> help on this, it would be ridiculously appreciated. I have already
> created this in Oracle and it works, but we don't want to have to pay
> the monster if something as wonderful as Postgres can handle it.
In addition to Rod's advice, please increase your checkpoint_segments and
checkpoint_timeout parameters and make sure that the pg_xlog is on a seperate
disk resource from the database.
--
--Josh
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, Ryan.D.Wager@mail.sprint.com
Subject: Re: query rewrite using materialized views
In-Reply-To: <200501041116.49197.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