Revision history [back]
PostgresQL is better because it supports transactions and full text search at the same time.
MySQL does not support both at once. MySQL has a few choices of data storage backends - and none of the backends supports those two things at simultaneously.
Postgres has very deep support of full text searching - including word stemming, thesaurus matching, ranking, etc.
Transactions help to keep data internally consistent and avoid race conditions - when two or more users read and write data simultaneously.
P.S. This site still runs or MySQL, my bad. If you use Postgres, the only visible change will be "sort by relevance" option in the question list, that will appear when some search term is typed. MySQL does not have ranking, so no such option.
PostgresQL is better because it supports transactions and full text search at the same time.
MySQL does not support both at once. MySQL has a few choices of data storage backends - and none of the backends supports those two things at simultaneously.
Postgres has very deep support of full text searching - including word stemming, thesaurus matching, ranking, etc.
Transactions help to keep data internally consistent and avoid race conditions - when two or more users read and write data simultaneously.
P.S. This site still runs or MySQL, my bad. If you use Postgres, the only visible change will be "sort by relevance" option in the question list, that will appear when some search term is typed. MySQL does not have ranking, so no such option.
PostgresQL is better because it supports transactions and full text search at the same time.
MySQL does not support both at once. MySQL has a few choices of data storage backends - and none of the backends supports those two things at simultaneously.
Postgres has very deep support of full text searching - including word stemming, thesaurus matching, ranking, etc.
Transactions help to keep data internally consistent and avoid race conditions - when two or more users read and write data simultaneously.