Re: Heavy postgres process

From: "Guido Barosio" <gbarosio(at)gmail(dot)com>
To: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
Cc: "Kenneth Marshall" <ktm(at)rice(dot)edu>, Vivek_Sharan <Vivek_Sharan(at)infosys(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Heavy postgres process
Date: 2008-09-17 19:43:46
Message-ID: f7f6b4c70809171243l72951796l94e3212f05829f00@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Getting to the latest 7.4 server involves the same as going to the
latest 8.x server, AFAIK, if we take in consideration that 7.4.8
requires a dump & restore (meaning downtime).

I would rather go after the latest 8.x server

2 cents.

(It seems that Vivek works for Infosys, and that may explain the
reason for an Oracle migration in the future. They are prolly plenty
of Oracle DBA's working there, cheaper and reusable for sure if you
think that often the kind of clients they handle are already
oracle'ized )

gb.-

On Wed, Sep 17, 2008 at 3:58 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Wed, Sep 17, 2008 at 12:31 PM, Kenneth Marshall <ktm(at)rice(dot)edu> wrote:
>> Gee,
>>
>> Going to Oracle does seem a bit like throwing the baby out with
>> the bath water.
>
> Especially considering the performance increase from pgsql 7.4 to 8.3
> is humongous. I'd say most operations are 2 to 4 times as fast and
> some operations are many 10 to 100 times faster.
>
> But for Vivek the real, first priority is to get his 7.4.5 server
> updated to the latest 7.4 version to make sure his data stays safe.
>

--
http://www.linkedin.com/in/gbarosio

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Marlowe 2008-09-17 20:07:45 Re: Heavy postgres process
Previous Message Scott Marlowe 2008-09-17 18:58:07 Re: Heavy postgres process