Re: [WIP] In-place upgrade - Mailing list pgsql-hackers

From Jeff
Subject Re: [WIP] In-place upgrade
Date
Msg-id 580C7B8A-3605-4DDF-96F7-B220FF4B19FE@torgo.978.org
Whole thread Raw
In response to Re: [WIP] In-place upgrade  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: [WIP] In-place upgrade  ("Robert Haas" <robertmhaas@gmail.com>)
List pgsql-hackers
On Nov 9, 2008, at 11:09 PM, Joshua D. Drake wrote:
>> I think it's time for people to stop asking for the moon and realize
>> that if we don't constrain this feature pretty darn tightly, we will
>> have *nothing at all* for 8.4.  Again.
>
> Gotta go with Tom on this one. The idea that we would somehow upgrade
> from 8.1 to 8.4 is silly. Yes it will be unfortunate for those running
> 8.1 but keeping track of multi version like that is going to be  
> entirely
> too expensive.
>

I agree as well. If we can get the at least the base level stuff in  
8.4 so that 8.5 and beyond is in-place upgradable then that is a huge  
win.   If we could support 8.2 or 8.3 or 6.5 :) that would be nice,  
but I think dealing with everything retroactively will cause our heads  
to explode and a mountain of awful code to arise.   If we say "8.4 and  
beyond will be upgradable" we can toss everything in we think we'll  
need to deal with it and not worry about the retroactive case (unless  
someone has a really clever(tm) idea!)

This can't be an original problem to solve, too many other databases  
do it as well.

--
Jeff Trout <jeff@jefftrout.com>
http://www.stuarthamm.net/
http://www.dellsmartexitin.com/





pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: SQL5 budget
Next
From: "Jonah H. Harris"
Date:
Subject: Re: WIP: Hash Join-Filter Pruning using Bloom Filters