From: Guy Rouillier <guyr-ml1@burntmail.com>
To: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: High update activity, PostgreSQL vs BigDBMS
Date: Sat, 06 Jan 2007 23:22:58 -0500
Message-ID: <45A075A2.9090906@burntmail.com> (raw)
In-Reply-To: <459F1421.9090905@modgraph-usa.com>
References: <45935A49.6080602@burntmail.com>
<bf54be870612280106n1247520dtb48e10cb4bdc43e9@mail.gmail.com>
<459F0EA6.30403@burntmail.com>
<459F1421.9090905@modgraph-usa.com>
Craig A. James wrote:
> I don't know if you have access to the application's SQL, or the time to
> experiment a bit, but unless your schema is trival and your SQL is
> boneheaded simple, you're not going to get equal performance from
> Postgres until you do some analysis of your application under real-world
> conditions, and optimize the problem areas.
Craig, thanks for taking the time to think about this. Yes, I have all
the application source code, and all the time in the world, as I'm doing
this experimentation on my own time. The test hardware is old stuff no
one intends to use for production work ever again, so I can use it as
long as I want.
The application is fairly straightforward, but as you say, what is
working okay with BigDBMS isn't working as well under PG. I'm going to
try other configuration suggestions made by others before I attempt
logic changes. The core logic is unchangeable; millions of rows of data
in a single table will be updated throughout the day. If PG can't
handle high volume updates well, this may be brick wall.
--
Guy Rouillier
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: guyr-ml1@burntmail.com
Subject: Re: High update activity, PostgreSQL vs BigDBMS
In-Reply-To: <45A075A2.9090906@burntmail.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