Re: [SL] upgrade issues...

[Roy W P. <arc...@mt...>]

On February 5, 2008, Dieter Simader wrote:
> duh, Roy, if this error does not happen in the upgrade from 2.6.27-2.8.0 
> but it happens in the upgrade 2.8.0-2.8.2 why should it be in the UPGRADE 
> docs for 2.6.27-2.8.0 ?
> 
But it DOES happen when upgrading from 2.6.27 to 2.8.12
I never meant to suggest it should be in the 2.6.27-2.8.0 doc

> BTW, this error was done delibertly so people wouldn't have to mess around 
> with the upgrade scripts. I could have left the oneliner which is in 
> Pg-upgrade-2.8.0-2.8.2.sql in the next upgrade script and have you edit
> the upgrade scripts instead.
> 
> Which is easier, load admin.pl, unlock the system and log in again or have 
> you edit the upgrade script?

obvious answer

FWIW
As you know, I own a copy of the manual and have used SL for a while. I'm familiar with the traditional upgrade process and yet...
I read the 2.6.27-2.8.0 upgrade docs and the readme that the setup script always gives the option to display, and didn't see a mention of the possible error.
I guess i could have read the 2.6.12-2.8.0 upgrade docs AND then  2.8.0-2.8.x upgrade docs, but it's not intuitive to read docs for a 2.8.0-2.8.12 upgrade when you aren't upgrading from 2.8.0...

That said, it would be a pain to keep having to create upgrade docs for every possible upgrade combination.
I'm someone who reads docs and yet I didn't read anything about the error being expected.  
Maybe stick a comment in the readme or FAQ ?  who knows....  

It's not a criticism so don't take it that way.  it's a suggestion in the interest of making things easier for everyone.
IMO, any way to prevent people from littering the list with questions to documented answers is a good thing.

Cheers,
Roy