pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Leif B. Kristensen <leif@solumslekt.org>
To: pgsql-advocacy@postgresql.org
Subject: Re: Avoiding upgrade backlash
Date: Wed, 14 Nov 2007 13:54:49 +0100
Message-ID: <200711141354.49400.leif@solumslekt.org> (raw)
In-Reply-To: <200711141228.33802.leif@solumslekt.org>
References: <200711121442.31233.josh@agliodbs.com>
	<20071113160041.GA19014@alvh.no-ip.org>
	<200711141228.33802.leif@solumslekt.org>

On Wednesday 14. November 2007, Leif B. Kristensen wrote:
>On Tuesday 13. November 2007, Alvaro Herrera wrote:
>>Leif B. Kristensen wrote:
>>> On Monday 12. November 2007, Josh Berkus wrote:
>>> >I'm thinking that we need to warn everyone about:
>>> >1) They need to use 8.3's pg_dump, not the old version, to upgrade
>>>
>>> Isn't there a chicken-and-egg problem here? On my Gentoo system, I
>>> have always been forced to uninstall the old version before
>>> upgrading to a new version.
>>
>>That's a Gentoo shortcoming, nothing more.
>
>I've started a thread about it in the Portage & Programming section of
>forums.gentoo.org:
>
>http://forums.gentoo.org/viewtopic-t-615494.html
>
>I hope that someone more knowledgeable than me will be able to
>contribute in bringing this issue to the attention of the Gentoo
>developers, and hopefully work out a solution. Sure, there are other
>Gentoo users than me around here?

FYI, I've filed a bug report on bugs.gentoo.org:

"This is not quite a bug, but rather an approaching challenge. See this 
thread on forums.gentoo.org 
[http://forums.gentoo.org/viewtopic-t-615494.html], in which I was 
asked to file a bug report. Concerning the upcoming PostgreSQL upgrade 
from 8.2 to 8.3, it's imperative that Gentoo implements an adequate 
transition procedure. Blocking the old version will create 
a 'chicken-and-egg' situation where you are left incapable of upgrading 
your existing databases. According to the developers, it's important 
that a dump of the old database should be done with the new 8.3 version 
of pg_dump. See this thread 
[http://archives.postgresql.org/pgsql-advocacy/2007-11/msg00051.php] on 
pgsql-advocacy for some details."

The bug id is [https://bugs.gentoo.org/show_bug.cgi?id=199142].
-- 
Leif Biberg Kristensen | Registered Linux User #338009
http://solumslekt.org/ | Cruising with Gentoo/KDE
My Jazz Jukebox: http://www.last.fm/user/leifbk/



view thread (37+ messages)  latest in thread

Message-ID: <200711141354.49400.leif@solumslekt.org>
Permalink:  ../200711141354.49400.leif@solumslekt.org/
Also on:    postgresql.org/message-id/200711141354.49400.leif@solumslekt.org

 · 

reply

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-docs@postgresql.org
  Cc: leif@solumslekt.org, pgsql-advocacy@postgresql.org
  Subject: Re: Avoiding upgrade backlash
  In-Reply-To: <200711141354.49400.leif@solumslekt.org>

* 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