blocks|key|1618395|text|选择你更熟悉的那个。MySQL与PostgreSQL是一场无休止的战争。这两个引擎都是优秀的数据库引擎，并且都被主要网站使用。这在实践中真的没什么关系。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1618396|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Go with whichever you're more familiar with. MySQL vs PostgreSQL is an endless war. Both of them are excellent database engines and both are being used by major sites. It really doesn't matter in practice.

blocks|key|1618437|text|此应用程序将托管在您自己的服务器上，还是由托管公司托管？如果您使用的是托管公司，请确保他们支持您选择的数据库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1618438|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Will this application be hosted on your own servers or by a hosting company? Make sure that if you are using a hosting company, they support the database of choice.

blocks|key|1403766|text|即使Postgresql看起来更好，我发现它在Django上也有一些性能问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1403767|Postgresql是用来处理“长连接”(连接池、持久连接等)的。|1403768|MySQL是用来处理“短连接”的(连接、查询、断开连接、has+some+performances+issues+with+a+lot+of+open+connections)|offset|length|1403769|问题是Django不支持连接池或持久连接，它必须在每次视图调用时连接/断开数据库。|1403770|它可以与Postgresql一起工作，但连接到Postgresql的成本要比连接到MySQL数据库多得多(在Postgresql上，每个连接都有自己的进程，这比在MySQL中弹出一个新线程要慢得多)。|1403771|然后，您将获得一些在某些情况下非常有用的功能，如查询缓存。(但你失去了PostgreSQL出色的文本搜索功能)|1403772|entityMap|0|LINK|mutability|MUTABLE|url|http://www.mysqlperformanceblog.com/2010/12/17/impact-of-the-number-of-idle-connections-in-mysql/^0|0|0|S|1N|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@$F|Y|G|Z|1|10]]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

Even if Postgresql looks better, I find it has some performances issues with Django:

Postgresql is made to handle "long connections" (connection pooling, persistant connections, etc.)

MySQL is made to handle "short connections" (connect, do your queries, disconnect, <a href="http://www.mysqlperformanceblog.com/2010/12/17/impact-of-the-number-of-idle-connections-in-mysql/" rel="noreferrer">has some performances issues with a lot of open connections</a>)

The problem is that Django does not support connection pooling or persistant connection, it has to connect/disconnect to the database at each view call.

It will works with Postgresql, but connecting to a Postgresql cost a LOT more than connecting to a MySQL database (On Postgresql, each connection has it own process, it's a lot slower than just popping a new thread in MySQL).

Then you get some features like the Query Cache that can be really useful on some cases. (But you lost the superb text search of PostgreSQL)

blocks|key|1403821|text|当在django-south迁移失败时，开发人员建议您不要使用MySQL：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1403822|!+The+South+developers+regret+this+has+happened,+and+would
!+like+to+gently+persuade+you+to+consider+a+slightly
!+easier-to-deal-with+DBMS+(one+that+supports+DDL+transactions)|code-block|syntax|javascript|1403823|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

When a migration fails in django-south, the developers encourage you not to use MySQL:

<pre><code>! The South developers regret this has happened, and would
! like to gently persuade you to consider a slightly
! easier-to-deal-with DBMS (one that supports DDL transactions)
</code></pre>

blocks|key|1403887|text|如果您打算使用db分发代码，这两个db之间存在一个主要的许可差异，这将影响您。MySQL的客户端库是GPL，而PostegreSQL的客户端库使用的是类似于BSD的许可，这可能更容易使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1403888|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

There is a major licensing difference between the two db that will affect you if you ever intend to distribute code using the db. MySQL's client libraries are GPL and PostegreSQL's is under a BSD like license which might be easier to work with.

blocks|key|1618715|text|由于我对MySQL非常熟悉(并且一直在努力寻找合适的安装器和快速测试postgreSQL缓慢的网络“工作台”界面，这让我望而却步)，在项目结束时，在部署几个月后，当我研究备份选项时，我发现你必须为MySQL的企业备份功能付费。在最后时刻抓住了你。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1618716|使用MySql，我不得不用Django编写一些丑陋的原始SQL查询，因为没有针对每个组的select+distinct来检索每个组的最新查询。我还在看postgreSQL的全文搜索，我真希望我用的是postgresSQL。|1618717|即使您熟悉MySQL，我也推荐您使用PostgreSQL，但您的使用里程可能会有所不同。|1618718|更新：DBeaver是MySql+Workbench图形用户界面工具的一个很好的等价物，但它与PostgreSQL+(以及其他许多通用数据库工具)配合得非常好。|offset|length|style|CODE|1618719|entityMap^0|0|0|0|3|7|B|F|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@$H|R|I|S|J|K]|$H|T|I|U|J|K]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

Having gone down the road of MySQL because I was familiar with it (and struggling to find a proper installer and a quick test of the slow web &quot;workbench&quot; interface of postgreSQL put me off), at the end of the project, after a few months after deployment, while looking into back up options, I see you have to pay for MySQL's enterprise back up features. Gotcha right at the very end.
With MySql I had to write some ugly monster raw SQL queries in Django because no select distinct per group for retrieving the latest per group query. Also looking at postgreSQL's full-text search and wishing I had used postgresSQL.
I recommend PostgreSQL even if you are familiar with MySQL, but your mileage may vary.
UPDATE: <code>DBeaver</code> is a great equivalent of <code>MySql Workbench</code> gui tool but works with PostgreSQL very nicely (and many others as its a universal DB tool).

My Django project is going to be backed by a large database with several hundred thousand entries, and will need to support searching (I'll probably end up using djangosearch or a similar project.)

Which database backend is best suited to my project and why? Can you recommend any good resources for further reading?

MySQL vs PostgreSQL? Which should I choose for my Django project?

我的Django项目将由一个包含数十万个条目的大型数据库支持，并且需要支持搜索(我最终可能会使用djangosearch或类似的项目)。哪个数据库后端最适合我的项目?为什么？你能推荐一些好的资源供你进一步阅读吗？

问MySQL vs PostgreSQL？我应该为我的Django项目选择哪一个？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MySQL vs PostgreSQL？我应该为我的Django项目选择哪一个？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MySQL vs PostgreSQL？我应该为我的Django项目选择哪一个？
EN