Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switching from MySQL to PostgreSQL in default install #71

Closed
Omeryl opened this issue Jun 25, 2015 · 12 comments
Closed

Switching from MySQL to PostgreSQL in default install #71

Omeryl opened this issue Jun 25, 2015 · 12 comments
Assignees
Milestone

Comments

@Omeryl
Copy link

Omeryl commented Jun 25, 2015

Any particular reason we're using Oracle's MySQL over better/nicer alternatives, like MariaDB?

@it33
Copy link
Contributor

it33 commented Jun 25, 2015

hi Omeryl, thanks for the question. We basically chose MySQL because of its popularity. It wasn't a value judgement, just using what people were most likely to find familiar.

@Omeryl
Copy link
Author

Omeryl commented Jun 25, 2015

Hey @it33, MariaDB is still MySQL, just completely open unlike Oracle's MySQL (it's actually a fork of MySQL maintained by the original developer of MySQL). It has major advantages over Oracle's MySQL.

https://mariadb.org/

@hauleth
Copy link

hauleth commented Jun 26, 2015

IMHO the nicest solution would be PostgreSQL

@ShawnMilo
Copy link

In many people's opinion's, PostgreSQL is a very good database, and MySQL is not, really. Also, very informative, short video of MySQL behaving unforgivably with its default configuration.

@it33
Copy link
Contributor

it33 commented Jun 27, 2015

@Omeryl, @hauleth, @ShawnMilo, I've added feature requests (http://www.mattermost.org/feature-requests/) for MariaDB and Postgres support at http://mattermost.uservoice.com/forums/306457-general/suggestions/8589295-support-for-mariadb and
http://mattermost.uservoice.com/forums/306457-general/suggestions/8589070-support-for-postgresql and made the first upvote on each.

Please consider joining the forum (one click with Twitter, Google or Facebook) to continue the discussion?

This is the third day of the open source project and your input as the earliest members of the community on this topic is highly appreciated.

Since these topics appear to be more feature requests than issues in the context of the project (http://www.mattermost.org/filing-issues/), I'm closing this thread so discussion can continue in the feature request forum.

@it33 it33 closed this as completed Jun 27, 2015
@Omeryl
Copy link
Author

Omeryl commented Jun 27, 2015

Meh, I don't think a Zendesk sufficiently satisfies things like this. It's an open source project, the first thing people will see is the "Issues" portion of the repo more than likely. Why not properly tag issues? @it33

@it33
Copy link
Contributor

it33 commented Jun 27, 2015

@Omeryl It's a good question.

I think ideally for feature requests we'd want to offer the community a way to vote on, search through and browse trending feature requests similar to http://feedback.gitlab.com/forums/176466-general/filters/hot

GitHub Issues doesn't seem to support what we believe we'll need long term--and I agree Zendesk doesn't either, it's just what we were using for the video game business, and was familiar.

It's starting to break already and maybe we should go to Uservoice for this. I wasn't sure how high priority that work was.

You're making us think a lot this week, @Omeryl. Thank you, don't stop :)

@it33
Copy link
Contributor

it33 commented Jul 3, 2015

After more community discussion and a feature request filing, the core team will be changing from MySQL in the default install to PostgreSQL for the 0.6.0 release at the end of the month: http://mattermost.uservoice.com/forums/306457-general/suggestions/8589070-support-for-postgresql

MariaDB was also considered, but it didn't end up as the top community choice.

@Omeryl, we're also switching to using GitHub issues with proper tags. Thanks again for your feedback. It took us a week, but we're finding our way now.

@it33 it33 reopened this Jul 3, 2015
@it33 it33 changed the title MySQL Switching from MySQL to PostgreSQL in default install Jul 3, 2015
@it33 it33 added this to the 0.6.0 milestone Jul 3, 2015
@kamilion
Copy link

kamilion commented Jul 3, 2015

Bleh, postgresql instead of rethinkdb? Seriously, you guys even mention them on your blog!

http://www.mattermost.org/on-premises-open-source-slack-alternative/

That was the whole reason I CAME, cause I thought I'd get a nice new rethinkdb project!

Oh well. At least it's postgresql, can't really complain there. Anything but mysql.

Such a shame -- rethinkdb totally fits the mattermost model to a T.
(incidentally, looks like gorethink made it's 1.0.0 release! yay!)
https://github.com/dancannon/gorethink/releases/tag/v1.0.0
Changefeeds are the best thing to ever happen to databases.
http://rethinkdb.com/docs/changefeeds/javascript/
http://rethinkdb.com/api/javascript/changes/
Why would you ever need a separate redis? 💻 🔨

@sun4sun
Copy link

sun4sun commented Jul 13, 2015

so, I'm can help with switching from MySQL to PostgreSQL.
also at this time can check possibilities about RethinkDB

@coreyhulen
Copy link
Contributor

@alexsun thanks. there is already a pull request submitted for postgresql.

@coreyhulen
Copy link
Contributor

postgres if fixed with #170

hanzei added a commit that referenced this issue Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants