| From: | Rob Wultsch <wultsch(at)gmail(dot)com> |
|---|---|
| To: | John Gage <jsmgage(at)numericable(dot)fr> |
| Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, "Wang, Mary Y" <mary(dot)y(dot)wang(at)boeing(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Need Some Recent Information on the Differences between Postgres and MySql |
| Date: | 2010-06-25 08:33:10 |
| Message-ID: | AANLkTimDgYr4sfxR-ZC8rioQxvd13nAsAQiPCQgg5wzj@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jun 25, 2010 at 1:22 AM, John Gage <jsmgage(at)numericable(dot)fr> wrote:
> There are features, are there not, that Postgres has that MySQL does not
> have?
>
> I refer in particular to things like tsvector.
>
> Am I mistaken in this?
>
> John
>
>
> On Jun 25, 2010, at 3:46 AM, Rob Wultsch wrote:
>
>> unless there was a specific reason to migrate
>
>
MySQL has several full text search solutions. The built in MyISAM
solution is the best known, but there is also an engine for using
sphinx.
...
And there are features that MySQL has that PG does not. Index only
queries is a massive feature. Pluggable backend storage engines are
another. MySQL is also somewhat simpler to tune.
Both systems can work well. Both have advantages. Both can suck.
As has been just demonstrated, both have communities that suck at
mingling with the other major open source rdms.
--
Rob Wultsch
wultsch(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2010-06-25 08:44:04 | Re: Need Some Recent Information on the Differences between Postgres and MySql |
| Previous Message | Dick Kniep | 2010-06-25 08:29:01 | Warnings after pg_dumpall > restore |