Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 8FC3C2E0221 for ; Wed, 12 Mar 2008 04:08:30 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 92166-05 for ; Wed, 12 Mar 2008 04:08:18 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by postgresql.org (Postfix) with ESMTP id 0865F2E01F9 for ; Wed, 12 Mar 2008 04:08:20 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id m38so3303054waf.5 for ; Wed, 12 Mar 2008 00:08:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=f+iI+N4OsHv2dqMVF/R0LgQv735rcy5udDpqEGiYIHU=; b=qsyCy6xqVyNmwKsE6/HH3YBAOCddCizYD+1NVy4lWqetdYpbs22x6Gzuxp6cESOOXu/aoG6OW+MzJGYVlbue/6CDYVOXPGNZH5qqj+Y7V3yVcSYIaClE/YqGBfkQBkOgQMvqH26DSe3RAs/uOJD6duZ2Dm6RpzmlT9f7t2Vw3mA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=HRUGlNg5AP19N5NO6FF63JjtsMb6sxnOafxerVeU0bcsuVlktR50L+sxxrQtnr4JbhSST/DmtAce6uiM1T+V36ByTJrMEaFp//+VsBlBxlbK3Rrszqifd0CzMOwGU8NLot+r+crpQcf5BW8fy5K6l5i/1pa7xykwIOjfh1M9gNc= Received: by 10.114.197.1 with SMTP id u1mr6315583waf.61.1205305699632; Wed, 12 Mar 2008 00:08:19 -0700 (PDT) Received: from ?10.1.1.19? ( [203.217.18.65]) by mx.google.com with ESMTPS id n22sm27742164pof.1.2008.03.12.00.08.18 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 12 Mar 2008 00:08:19 -0700 (PDT) Message-ID: <47D780D0.2090702@gmail.com> Date: Wed, 12 Mar 2008 18:05:52 +1100 From: Chris User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: david@lang.hm CC: pgsql-performance@postgresql.org Subject: Re: migration of 7.4 to 8.1 References: <47D76AFA.7020100@postnewspapers.com.au> <47D7780B.3080001@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/252 X-Sequence-Number: 29206 david@lang.hm wrote: > On Wed, 12 Mar 2008, sathiya psql wrote: > >> In the home page itself they were saying .... testing ... unstable.... > > you are talking about the debian home page right? > >> then we should not use that for live..... >> >> so i prefer 8.1 ......... > > Debian selected the version of Postgres for Etch about a year and a half > ago. At that point selecting 8.1 was a resonable choice. > > Debian has a policy that they will never change the version number of a > package in a stable release (they will backport many bugfixes, but not > upgrade the version) > > As a result 2 years from now when Postgres is on 8.5 stable (and looking > at 8.6), Debian Etch will still be on 8.1 I like that with debian I can install multiple postgres versions and it handles everything for me :) Changing the default port, config files are in different folders, different start up scripts.. all works very nicely :) Which means you can have 8.1 installed and 8.3 installed at the same time - both from packages, no compiling etc necessary - and can switch between them very easily. -- Postgresql & php tutorials http://www.designmagick.com/