From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: Piñeiro <apinheiro@igalia.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance problem with Sarge compared with Woody
Date: Tue, 12 Sep 2006 09:28:43 -0500
Message-ID: <1158071323.1854.29.camel@state.g2switchworks.com> (raw)
In-Reply-To: <b42b73150609111853p38826ff0ncca31784dd7e92a9@mail.gmail.com>
References: <1157998456.7540.15.camel@codfix.local.igalia.com>
<1158012220.1854.10.camel@state.g2switchworks.com>
<b42b73150609111853p38826ff0ncca31784dd7e92a9@mail.gmail.com>
On Mon, 2006-09-11 at 20:53, Merlin Moncure wrote:
> On 9/11/06, Scott Marlowe <smarlowe@g2switchworks.com> wrote:
> > I'd suggest two things.
> >
> > one: Get a better ERP... :) or at least one you can inject some
> > intelligence into, and two: upgrade to postgresql 8.1, or even 8.2 which
> > will be released moderately soon, and if you won't be going into
> > production directly, might be ready about the time you are.
>
> for 3 months I ran a 400M$ manufacturing company's erp off of a
> pre-beta 8.0 windows pg server converted from cobol using some hacked
> out c++ middleware. I remember having to change how the middleware
> handled transactions when Alvaro changed them to a checkpoint
> mechanism. I also remember being relieved when I no longer had to
> manually edit pg_config.h so nobody would notice they would notice
> they were running a beta version of postgresql had one of the
> technical people casually logged into psql. I scraped out almost
> completely unscathed except for a nasty crash due to low stack
> allocation of the compiler on windows.
>
> the point of all this? get onto a recent version of postgresql, what
> could possbily go wrong?
You did notice I mentioned that it would only make sense if they weren't
going into production right away. I.e. develop the app while pgdg
develops the database, and release at about the same time.
I wouldn't put 8.2 into production just yet, but if I had a launch date
of next spring, I'd certainly consider developing on it now.
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: smarlowe@g2switchworks.com, mmoncure@gmail.com, apinheiro@igalia.com
Subject: Re: Performance problem with Sarge compared with Woody
In-Reply-To: <1158071323.1854.29.camel@state.g2switchworks.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