From: david@lang.hm
To: Craig Ringer <craig@postnewspapers.com.au>
Cc: sathiya psql <sathiya.psql@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: migration of 7.4 to 8.1
Date: Tue, 11 Mar 2008 23:39:40 -0700 (PDT)
Message-ID: <alpine.DEB.1.00.0803112338210.943@asgard.lang.hm> (raw)
In-Reply-To: <47D77929.7030401@postnewspapers.com.au>
References: <f966c2ee0803112227y7c969d52pea8e228ed0fbbdf3@mail.gmail.com>
<47D76AFA.7020100@postnewspapers.com.au>
<f966c2ee0803112324m7c863501kd6e33bc5b44ca010@mail.gmail.com>
<47D77929.7030401@postnewspapers.com.au>
On Wed, 12 Mar 2008, Craig Ringer wrote:
> sathiya psql wrote:
>>> This might be a silly question, but ... why 8.1 ?
>>>
>>> If you're doing a major upgrade, why not go straight to 8.3? It's been
>>> out long enough that there aren't any obvious nasty bugs, and there have
>>> been a fair few fixes and improvements since prior versions.
>>>
>> Because am using Debian ETCH stable... i need to continue using this... In
>> Debian ETCH stable 8.1 is only there....
>
> I use Etch on my servers. The magic of etch-backports from backports.org
> allows me to use 8.3 without messing with anything else. It works extremely
> well.
>
> All I had to do to install 8.3 was add the etch-backports line to my
> /etc/apt/sources.list, run `apt-get update', then run:
>
> apt-get -t etch-backports install postgresql-8.3
>
> ... then migrate the data to it and remove the old packages.
>
> See backports.org for a mirror list.
>
>> I will be installing my project in other machines where it is having DEBIAN
>> ETCH STABLE, i dont want to face any problems... so only...
>>
>> am i right ???
>
> Personally I'd use 8.3 from backports.org, but it's of course up to you.
consider the fact that after 1 year Etch is 2 major releases out of date.
by the time the next stable release is made you will be running on ancient
versions unless you make use of backports.org (or compile it yourself,
which is useually my choice).
David Lang
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: david@lang.hm, craig@postnewspapers.com.au, sathiya.psql@gmail.com
Subject: Re: migration of 7.4 to 8.1
In-Reply-To: <alpine.DEB.1.00.0803112338210.943@asgard.lang.hm>
References: <f966c2ee0803112227y7c969d52pea8e228ed0fbbdf3@mail.gmail.com> <47D76AFA.7020100@postnewspapers.com.au> <f966c2ee0803112324m7c863501kd6e33bc5b44ca010@mail.gmail.com> <47D77929.7030401@postnewspapers.com.au> <alpine.DEB.1.00.0803112338210.943@asgard.lang.hm>
* 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