Re: upgrading SL 2.6.27 --> LSMB 1.1.2

[david <..hidden..>]

david wrote:
> Chris Travers wrote:
> > On Wed, Sep 10, 2008 at 7:04 PM, david <..hidden..> wrote:
> >
> >
> > > > Pg-upgrade-2.6.12-2.6.17.sql
> > > > Pg-upgrade-2.6.17-2.6.18.sql
> > > > Pg-upgrade-2.6.18-2.6.19.sql
> > > Thanks... but..... ;-)
> > >
> > > I'm already in SL 2.6.27... doesn't that mean these are not required?
> > > (see subject line)
> > >
> > > thanks for you excellent work and help.
> >
> > If you:
>
> select dbversion from defaults; [1]
>
> > you will get 2.6.12, hence the scripts to run.
>
> hmm... that is SO counter-intuitive! So the database version is 2.6.12 
> and I have to upgrade to 2.6.19 even though I'm running SL 2.6.27
> Is that documented?
>
> At the risk of appearing ungrateful, shouldn't that instruction to run 
> the Pg_upgrade files be included in README.sql-ledger?
>
> Next problem is that Pg-upgrade-2.6.18-2.6.19.sql file does not exist.


I found it in the LSMB 1.2 tarball. does this mean it only applies to 
1.2.x ?

Sorry for the endless questions, but I don't want to end up with a 
corrupted database.



> I'm using LSMB 1.1.2 btw ... not  1.12 as originally in my subject line.
>
> many thanks....
>
> david
>
> [1] select version from defaults;