Mailing List Archive: upgrade from 3.1.6 to latest

upgrade from 3.1.6 to latest

Sep 29, 2014, 11:59 AM

Post #1 of 4 (1267 views)

Hi list,

Can I upgrade from 3.1.6 to 3.2 without touching/upgrading the postgres
DB? (the DB is a separate server)
And will there be a problem if I run the new 3.2 on a test setup while
keeping the current 3.1.6 online during test phase?

Regards,
Marius

dbmail-util -V
This is DBMail version 3.1.6
But actually I think the version number is falsely reported as the
source tree is dbmail-3.1.7.

upgrade from 3.1.6 to latest [ In reply to ]

rogerio at porta80

Oct 30, 2014, 1:11 PM

Post #2 of 4 (1211 views)

Permalink

Hi,

I also need to deploy Dbmail 3.2. But I need to share the same PgSQL 9.3 DB with another Dbmail 3.1.17.

Is it possible?

There are 4 SQL updates needed to install Dbmail 3.2, mostly index changes and new columns to dbmail tables.

Regards.

Rogerio

Re: upgrade from 3.1.6 to latest [ In reply to ]

lordvan at lordvan

Oct 31, 2014, 2:38 AM

Post #3 of 4 (1212 views)

Permalink

Am 30.10.2014 um 21:11 schrieb Rogerio Pereira:
> Hi,
>
> I also need to deploy Dbmail 3.2. But I need to share the same PgSQL 9.3
> DB with another Dbmail 3.1.17.
>
> Is it possible?
>
> There are 4 SQL updates needed to install Dbmail 3.2, mostly index
> changes and new columns to dbmail tables.
>
> Regards.
>
> Rogerio
>
I am not sure if it would work, but I personally would not risk it (just
index changes would be one thing i guess, but added columns .. )
That said it might work *if* (and i do not know that) the SELECT queries
all specify the columns (as oppsoed to SELECT * ) *and* the new columns
have default values that would be filled correctly in case of update/insert.

if you really need to do this i suggest extensive testing.

_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Re: upgrade from 3.1.6 to latest [ In reply to ]

paul at nfg

Nov 2, 2014, 5:57 AM

Post #4 of 4 (1203 views)

Permalink

On 31-10-14 10:38, Thomas Raschbacher wrote:
> Am 30.10.2014 um 21:11 schrieb Rogerio Pereira:
>> Hi,
>>
>> I also need to deploy Dbmail 3.2. But I need to share the same PgSQL 9.3
>> DB with another Dbmail 3.1.17.
>>
>> Is it possible?
>>
>> There are 4 SQL updates needed to install Dbmail 3.2, mostly index
>> changes and new columns to dbmail tables.

If you run a dbmail-3.2, the upgrade steps will be performed
automatically. None of them are incompatible, with the possible
exception of dbmail_subjectfield (a view that is only used for
base-subject threading which nobody uses)

The dbmail_messages.seq field is simply not used by 3.1 - it's for
CONDSTORE and QRESYNC, and improved IDLE behaviour.

The changes on the dbmail_users table is for a special feature
(README.security-password) and not used by 3.1

> if you really need to do this i suggest extensive testing.

That is always good advise.

--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, github, linkedin
www.nfg.nl/info@nfg.nl/+31.85.877.99.97
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail