Database Schema - v3.2.1 to v3.3.3
Hello.
Have 4 Debian servers running Mailman3 v3.2.1 and sharing the same external MySql databases for Mailman3 and Mailman3-web. I am in the process of migrating to v3.3.3. It would be easiest to perform this upgrade one server at a time, but this would mean that for a short time I would have v3.2.1 and v3.3.3 using the same databases.
I am wondering if there are any MySql schema differences between the two versions. If there are, having the two different versions 'cohabitating' won't work..
Thanks.
-Dave
-- Dave Hall Binghamton University
On 4/4/23 21:28, Dave Hall via Mailman-users wrote:
Hello.
Have 4 Debian servers running Mailman3 v3.2.1 and sharing the same external MySql databases for Mailman3 and Mailman3-web. I am in the process of migrating to v3.3.3. It would be easiest to perform this upgrade one server at a time, but this would mean that for a short time I would have v3.2.1 and v3.3.3 using the same databases.
I am wondering if there are any MySql schema differences between the two versions. If there are, having the two different versions 'cohabitating' won't work..
As far as the Mailman3 database is concerned there are at least 3 migrations between 3.2.1 and 3.3.3 in mailman/database/alembic/versions. Namely: 2d2d0ef0828f_add_tag_column.py, 83339e4039da_add_usenet_watermark.py and d151c0b8d6f7_bounce_parameters.py.
As far as Mailman3-web is concerned, this is presumably a Debian/Ubuntu Mailman3-web package upgrade. There may be migrations in django_mailman3/migrations/, hyperkitty/migrations/ and postorius/migrations/ that affect this depending on what the specific version updates are in that upgrade.
In any case, there are schema differences for Mailman core between 3.2.1 and 3.3.3.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Apr 5, 2023 at 7:29 AM Dave Hall via Mailman-users < mailman-users@mailman3.org> wrote:
Hello.
Have 4 Debian servers running Mailman3 v3.2.1 and sharing the same external MySql databases for Mailman3 and Mailman3-web. I am in the process of migrating to v3.3.3. It would be easiest to perform this upgrade one server at a time, but this would mean that for a short time I would have v3.2.1 and v3.3.3 using the same databases.
You could {dup|trip|quadrup|-locate the databases and point each server to a different one temporarily.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
participants (3)
-
Dave Hall
-
Mark Sapiro
-
Odhiambo Washington