Re: [pgsql-advocacy] PostgreSQL versus MySQL for GPS Data - Mailing list pgsql-general

From Scott Marlowe
Subject Re: [pgsql-advocacy] PostgreSQL versus MySQL for GPS Data
Date
Msg-id dcc563d10904212027o618587efh9f84966726c2d57e@mail.gmail.com
Whole thread Raw
In response to Re: [pgsql-advocacy] PostgreSQL versus MySQL for GPS Data  (Steve Singer <ssinger_pg@sympatico.ca>)
List pgsql-general
On Tue, Apr 21, 2009 at 9:19 PM, Steve Singer <ssinger_pg@sympatico.ca> wrote:
> On Tue, 21 Apr 2009, David Fetter wrote:
>
>> On Tue, Apr 21, 2009 at 08:15:00PM +0100, Peter Childs wrote:
>>>
>>> Hmm Interestingly OSM have just switched from MySQL to PostgreSQL.
>>
>> Can we get somebody from OSM to talk about this on the record?
>
> I've forwarded this request the to the OSM talk list.  Hopefully someone who
> can talk 'on the record' will step forward.
>
> The master OSM database used for editing used to by MySQL but most of the
> map rendering was done from Postgis hosted data.  Over the weekend they
> switched ,as part of an API upgrade,  the main editing database to
> Postgresql (but still not using complex geometry types).
>
> I think the reasoning had to do with them wanting transactions and the
> switch to InnoDB brought has some downsides, but I don't know which of the
> innodb downsides motivated the switch.

I believe it was the loss of full text indexing with innodb that drove
the switch.  That's what the wiki entry on postgres says

> I think the reference to MonetDB was part of an April fools joke.

Sounds like it.  Still kinda freaked me out at first.

pgsql-general by date:

Previous
From: Steve Singer
Date:
Subject: Re: [pgsql-advocacy] PostgreSQL versus MySQL for GPS Data
Next
From: Bill Todd
Date:
Subject: No connection could be made because the target machine actively refused it