From: Josh Berkus <josh@agliodbs.com>
To: Steve Atkins <steve@blighty.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance suggestions for an update-mostly database?
Date: Mon, 4 Oct 2004 12:02:03 -0700
Message-ID: <200410041202.03548.josh@agliodbs.com> (raw)
In-Reply-To: <20041004180036.GA26390@gp.word-to-the-wise.com>
References: <20041004174019.GA25671@gp.word-to-the-wise.com>
<200410041038.14571.josh@agliodbs.com>
<20041004180036.GA26390@gp.word-to-the-wise.com>
Steve,
> In some ways something like Berkeley DB might be a better match to the
> frontend, but I'm comfortable with PostgreSQL and prefer to have the
> power of SQL commandline for when I need it.
Well, if data corruption is not a concern, you can always turn off
checkpointing. This will save you a fair amount of overhead.
You could also look at telegraphCQ. It's not prodcucton yet, but their idea
of "streams" as data sources really seems to fit with what you're talking
about.
--
--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, steve@blighty.com
Subject: Re: Performance suggestions for an update-mostly database?
In-Reply-To: <200410041202.03548.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