Menu
▾
▴
sql-ledger-users
|
From: david <da...@ke...> - 2008-07-23 04:06:43
|
I'm thinking of migrating sql-ledger from 2.6.27 / postgresql 8.1 to 2.8.16 / postgresql 8.3 Are there any migration issues during the transition? In other words, will the pg-dump from SL 2.6.27 / pg 8.1 talk nicely to pg 8.3? Or do I have to upgrade via pg 8.1, and the go to pg 8.3 at the last step? thanks David. |
|
From: Michael H. <mh...@it...> - 2008-07-23 05:09:35
|
Don't remember the exact revs but we jumped from 2.6.x to 2.8.x some months ago with no problems other than the reporting issue which I've covered exhaustively in another thread and that turned out to be because we were still on postgresql 7.x so I wouldn't expect that to be an issue for you. Thanks, Michael On Jul 22, 2008, at 9:06 PM, david wrote: > I'm thinking of migrating sql-ledger from 2.6.27 / postgresql 8.1 to > 2.8.16 / postgresql 8.3 > > Are there any migration issues during the transition? In other words, > will the pg-dump from SL 2.6.27 / pg 8.1 talk nicely to pg 8.3? Or > do I > have to upgrade via pg 8.1, and the go to pg 8.3 at the last step? > > thanks > > > David. > > > ---------------------------------------------------------------------- > --- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > sql-ledger-users mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users |
|
From: <la...@cl...> - 2008-07-23 06:57:25
|
Hello David: Back in May we had upgraded our production system from RH7.3/Postgresql7.x/SL2.4 to Centos5.2/Postgresql8.3.1(now at 8.3.3)/SL2.8.14(now at 2.8.16). Everything worked out nicely and it's been couple months now (with two proven monthends). The main thing was please make sure to use the newer 8.3 tools to do the dump, and to use the same database encoding for the upgrade. Some extra info. when we upgraded Postgres from 8.3.1 to 8.3.3 it was just a simply binary upgrade without the need to touch the data. We also had rolled out slony replication on the production cluster and production issues had yet to creep up, but we also had only replicated tables that were relevant to the IC module. You should be alright with the 8.1 -> 8.3 upgrade. Regards, Tim > I'm thinking of migrating sql-ledger from 2.6.27 / postgresql 8.1 to > 2.8.16 / postgresql 8.3 > > Are there any migration issues during the transition? In other words, > will the pg-dump from SL 2.6.27 / pg 8.1 talk nicely to pg 8.3? Or do I > have to upgrade via pg 8.1, and the go to pg 8.3 at the last step? > > thanks > > > David. > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > sql-ledger-users mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users > |
|
From: Paul T. <pt...@wa...> - 2008-07-23 17:04:57
|
I remember seeing something in the release notes regarding 'fix behaviour in postgresql 8.3. So I suggest to first upgrade Ledger, then upgrade postgres. No need to invite known bugs to the party, right? 2008/7/23 <la...@cl...>: > Hello David: > > Back in May we had upgraded our production system from > RH7.3/Postgresql7.x/SL2.4 to Centos5.2/Postgresql8.3.1(now at > 8.3.3)/SL2.8.14(now at 2.8.16). Everything worked out nicely and it's been > couple months now (with two proven monthends). The main thing was please > make sure to use the newer 8.3 tools to do the dump, and to use the same > database encoding for the upgrade. > > Some extra info. when we upgraded Postgres from 8.3.1 to 8.3.3 it was just > a simply binary upgrade without the need to touch the data. We also had > rolled out slony replication on the production cluster and production > issues had yet to creep up, but we also had only replicated tables that > were relevant to the IC module. > > You should be alright with the 8.1 -> 8.3 upgrade. > > Regards, > > Tim > > > > > I'm thinking of migrating sql-ledger from 2.6.27 / postgresql 8.1 to > > 2.8.16 / postgresql 8.3 > > > > Are there any migration issues during the transition? In other words, > > will the pg-dump from SL 2.6.27 / pg 8.1 talk nicely to pg 8.3? Or do I > > have to upgrade via pg 8.1, and the go to pg 8.3 at the last step? > > > > thanks > > > > > > David. > > > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move Developer's > > challenge > > Build the coolest Linux based applications with Moblin SDK & win great > > prizes > > Grand prize is a trip for two to an Open Source event anywhere in the > > world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > > sql-ledger-users mailing list > > sql...@li... > > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users > > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > sql-ledger-users mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users > > |
|
From: Michael H. <mh...@it...> - 2008-07-23 17:19:35
|
And backups! Lots of backups - at every step! :) Thanks, Michael On Jul 23, 2008, at 10:04 AM, Paul Tammes wrote: > I remember seeing something in the release notes regarding 'fix > behaviour in > postgresql 8.3. > So I suggest to first upgrade Ledger, then upgrade postgres. No > need to > invite known bugs to the party, right? > > 2008/7/23 <la...@cl...>: > >> Hello David: >> >> Back in May we had upgraded our production system from >> RH7.3/Postgresql7.x/SL2.4 to Centos5.2/Postgresql8.3.1(now at >> 8.3.3)/SL2.8.14(now at 2.8.16). Everything worked out nicely and >> it's been >> couple months now (with two proven monthends). The main thing was >> please >> make sure to use the newer 8.3 tools to do the dump, and to use >> the same >> database encoding for the upgrade. >> >> Some extra info. when we upgraded Postgres from 8.3.1 to 8.3.3 it >> was just >> a simply binary upgrade without the need to touch the data. We >> also had >> rolled out slony replication on the production cluster and production >> issues had yet to creep up, but we also had only replicated tables >> that >> were relevant to the IC module. >> >> You should be alright with the 8.1 -> 8.3 upgrade. >> >> Regards, >> >> Tim >> >> >> >>> I'm thinking of migrating sql-ledger from 2.6.27 / postgresql 8.1 to >>> 2.8.16 / postgresql 8.3 >>> >>> Are there any migration issues during the transition? In other >>> words, >>> will the pg-dump from SL 2.6.27 / pg 8.1 talk nicely to pg 8.3? >>> Or do I >>> have to upgrade via pg 8.1, and the go to pg 8.3 at the last step? >>> >>> thanks >>> >>> >>> David. >>> >>> >>> -------------------------------------------------------------------- >>> ----- >>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>> challenge >>> Build the coolest Linux based applications with Moblin SDK & win >>> great >>> prizes >>> Grand prize is a trip for two to an Open Source event anywhere in >>> the >>> world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> _______________________________________________ >>> sql-ledger-users mailing list >>> sql...@li... >>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users >>> >> >> >> >> --------------------------------------------------------------------- >> ---- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win >> great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in >> the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> sql-ledger-users mailing list >> sql...@li... >> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users >> >> > ---------------------------------------------------------------------- > --- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > sql-ledger-users mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users |
|
From: <la...@cl...> - 2008-07-23 20:42:09
|
good point...it definitely was not a single straight shot upgrade. like my one year old it was a crawl, walk, and run approach and we were ready to "crawl" again if the "walk" had failed. I think SL was upgraded before Postgres, and we had to go to 8.x because we needed to implement Slony. Plus, based on our upgarde history it will probably be another 3+ years before there will be another upgarde again...I hope not...Tim > I remember seeing something in the release notes regarding 'fix behaviour > in > postgresql 8.3. > So I suggest to first upgrade Ledger, then upgrade postgres. No need to > invite known bugs to the party, right? > > 2008/7/23 <la...@cl...>: > >> Hello David: >> >> Back in May we had upgraded our production system from >> RH7.3/Postgresql7.x/SL2.4 to Centos5.2/Postgresql8.3.1(now at >> 8.3.3)/SL2.8.14(now at 2.8.16). Everything worked out nicely and it's >> been >> couple months now (with two proven monthends). The main thing was please >> make sure to use the newer 8.3 tools to do the dump, and to use the same >> database encoding for the upgrade. >> >> Some extra info. when we upgraded Postgres from 8.3.1 to 8.3.3 it was >> just >> a simply binary upgrade without the need to touch the data. We also had >> rolled out slony replication on the production cluster and production >> issues had yet to creep up, but we also had only replicated tables that >> were relevant to the IC module. >> >> You should be alright with the 8.1 -> 8.3 upgrade. >> >> Regards, >> >> Tim >> >> >> >> > I'm thinking of migrating sql-ledger from 2.6.27 / postgresql 8.1 to >> > 2.8.16 / postgresql 8.3 >> > >> > Are there any migration issues during the transition? In other words, >> > will the pg-dump from SL 2.6.27 / pg 8.1 talk nicely to pg 8.3? Or do >> I >> > have to upgrade via pg 8.1, and the go to pg 8.3 at the last step? >> > >> > thanks >> > >> > >> > David. >> > >> > >> > ------------------------------------------------------------------------- >> > This SF.Net email is sponsored by the Moblin Your Move Developer's >> > challenge >> > Build the coolest Linux based applications with Moblin SDK & win great >> > prizes >> > Grand prize is a trip for two to an Open Source event anywhere in the >> > world >> > http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> > _______________________________________________ >> > sql-ledger-users mailing list >> > sql...@li... >> > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users >> > >> >> >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> sql-ledger-users mailing list >> sql...@li... >> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users >> >> > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > sql-ledger-users mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users > |
|
From: Michael H. <mh...@it...> - 2008-07-23 22:10:31
|
IT industry life cycle is 6mo-1yr, business technology life cycle is
3-5yrs.
This is half of what keeps IT consultants in business, somebody
has to be around to bridge the gap! :)
Thanks,
Michael
On Jul 23, 2008, at 1:42 PM, la...@cl... wrote:
> good point...it definitely was not a single straight shot upgrade.
> like my
> one year old it was a crawl, walk, and run approach and we were
> ready to
> "crawl" again if the "walk" had failed. I think SL was upgraded before
> Postgres, and we had to go to 8.x because we needed to implement
> Slony.
> Plus, based on our upgarde history it will probably be another 3+
> years
> before there will be another upgarde again...I hope not...Tim
>
>> I remember seeing something in the release notes regarding 'fix
>> behaviour
>> in
>> postgresql 8.3.
>> So I suggest to first upgrade Ledger, then upgrade postgres. No
>> need to
>> invite known bugs to the party, right?
>>
>> 2008/7/23 <la...@cl...>:
>>
>>> Hello David:
>>>
>>> Back in May we had upgraded our production system from
>>> RH7.3/Postgresql7.x/SL2.4 to Centos5.2/Postgresql8.3.1(now at
>>> 8.3.3)/SL2.8.14(now at 2.8.16). Everything worked out nicely and
>>> it's
>>> been
>>> couple months now (with two proven monthends). The main thing was
>>> please
>>> make sure to use the newer 8.3 tools to do the dump, and to use
>>> the same
>>> database encoding for the upgrade.
>>>
>>> Some extra info. when we upgraded Postgres from 8.3.1 to 8.3.3 it
>>> was
>>> just
>>> a simply binary upgrade without the need to touch the data. We
>>> also had
>>> rolled out slony replication on the production cluster and
>>> production
>>> issues had yet to creep up, but we also had only replicated
>>> tables that
>>> were relevant to the IC module.
>>>
>>> You should be alright with the 8.1 -> 8.3 upgrade.
>>>
>>> Regards,
>>>
>>> Tim
>>>
>>>
>>>
>>>> I'm thinking of migrating sql-ledger from 2.6.27 / postgresql
>>>> 8.1 to
>>>> 2.8.16 / postgresql 8.3
>>>>
>>>> Are there any migration issues during the transition? In other
>>>> words,
>>>> will the pg-dump from SL 2.6.27 / pg 8.1 talk nicely to pg 8.3?
>>>> Or do
>>> I
>>>> have to upgrade via pg 8.1, and the go to pg 8.3 at the last step?
>>>>
>>>> thanks
>>>>
>>>>
>>>> David.
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> ------
>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>>> challenge
>>>> Build the coolest Linux based applications with Moblin SDK & win
>>>> great
>>>> prizes
>>>> Grand prize is a trip for two to an Open Source event anywhere
>>>> in the
>>>> world
>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>>> _______________________________________________
>>>> sql-ledger-users mailing list
>>>> sql...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -----
>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>> challenge
>>> Build the coolest Linux based applications with Moblin SDK & win
>>> great
>>> prizes
>>> Grand prize is a trip for two to an Open Source event anywhere in
>>> the
>>> world
>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>> _______________________________________________
>>> sql-ledger-users mailing list
>>> sql...@li...
>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>
>>>
>> ---------------------------------------------------------------------
>> ----
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win
>> great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the
>> world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>
>
>
>
> ----------------------------------------------------------------------
> ---
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X