Mattermost v8.0+ and PostgreSQL

[girish]

https://github.com/mattermost/mattermost/issues/18351 is tracking how to migrate.

https://docs.mattermost.com/manage/bulk-export-tool.html and https://docs.mattermost.com/onboard/bulk-loading-data.html is possible the way to migrate but it says it doesn't migrate everything.

[girish]

@c0decafe said in Mattermost v8.0+ and PostgreSQL:

Any plans to migrate the cloudron mattermost app to PostgreSQL in the near future?

yes, we will also move. Though the migration won't be automatic. I think we will just push a new package.

[c0decafe]

@girish great, thank you. would be glad to help with testing or packaging.

[mtd-sales]

I am running Cloudron for 10+ paying customers and counting. One of the reasons how I convince them to use Cloudron is the maintenance of their open source software. All of them use mostly Mattermost. Obviously I’m not too happy that you don’t offer a migration path and make us do the work manually.

[girish]

@mtd-sales you have to ask Mattermost team to provide a proper a migration path, this is not something we (cloudron team) can do. We just package the app.

https://github.com/mattermost/mattermost/issues/18351 is the upstream issue.

[mtd-sales]

@girish I understand, thank you. Looks like they are working on a migration path. So I would prefer to wait before packaging a new one.

[ericdrgn]

@girish Don't know if this helps at all but someone added a great guide on the upstream issue. https://github.com/mattermost/mattermost/issues/18351#issuecomment-1682072226

[ericdrgn]

@girish looks like that issue https://github.com/mattermost/mattermost/issues/18351 is officially closed as the migration path is documented and successful at this point.

[girish]

@ericdrgn thanks. https://github.com/mattermost/docs/blob/master/source/deploy/postgres-migration.rst are the instructions it seems.

I am thinking of the below:

• pgLoader, morph and dbcmp tools can be preinstalled into the package.
• New installations will use postgres automatically
• Existing package will be converted to contain access to both a postgres and mysql database. Users have to follow the upstream docs to migrate.

Thoughts?

[ericdrgn]

That's probably the best way to do it, if anyone doesn't necessarily care about the data in mattermost they can just archive the mysql version and spin up a new one that automatically uses postgres, otherwise the migration steps aren't crazy if maintaining the data is important.

[joestarrd]

@girish said in Mattermost v8.0+ and PostgreSQL:

New installations will use postgres automatically

Was this implemented? We ran into the same problem but noticed new installations are still not using Postgres.

[girish]

@joestarrd not yet. Currently, the postgresql is going through some updates related to immich and discourse. We have to sort out the issues there before we attempt to move mattermost to postgres and test how compatible it is.

[joestarrd]

@girish understood, thank you for the quick update.

[cvachery]

Any update on this topic?
I've had to stop a migration from a non-cloudron instance to cloudron because of this issue

[girish]

I checked their docs and the forum and afaict MySQL is not deprecated. I found nothing in their docs atleast. https://docs.mattermost.com/deploy/postgres-migration.html is quite complicated but it does say PostgreSQL is preferred. We have many users using Mattermost and it would be too much work to make them migrate, especially since it is still supported upstream. Do you know any timeline of deprecation? Upstream docs don't mention anything about deprecation from what I tried to find.

[c0decafe]

This is the original reference:

• https://github.com/mattermost/mattermost-plugin-ai/issues/19#issuecomment-1609352822

Basically the AI plugin will only be available on postgresql.

Furthermore, others plugins are dropping mysql support accordingly, ie:

• https://github.com/mattermost/mattermost-plugin-msteams/pull/482

I don't think anyone expects a smooth migration of their existing instance but it would great if we can get a supported postgresql package.

[cvachery]

Wouldn't it be possible to have an option passed to the Cloudron to let the user choose if he wants to use postgres or mysql?

[Lanhild]

@girish what about having a new Mattermost package, with the same name as the current one and shipping with postgresql.

The current package (with MySQL) would have mysql somewhere in it's name, and then allow users to install whichever version they wish.

Other than that, it looks like they are (or will be) abandoning MySQL support slowly

[chymian]

@girish the AI bot is getting more and more essential for daily work.
any chance we get a postgresql version as supposed from @Lanhild for a fresh install?

@girish said in Mattermost v8.0+ and PostgreSQL:
New installations will use postgres automatically

which is not the case till 9.7.4

[girish]

@chymian we have not made this move yet. It requires obsoleting the old package and moving to postgres. And yet, there is no easy way on mattermost side to switch databases. Essentially, we will have to abandon all our existing mattermost installation base. It's a difficult decision to make. Maintaining two separate packages while possible is just additional work for a single app. We have to make separate tests and packages for every mm release.