addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1light-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Re: [newtech-1] Music Industry

From: Jonathan V.
Sent on: Monday, March 3, 2008 2:15 PM
On Mar 3, 2008, at 12:48 PM, Michael Mellinger wrote:

>   Did you ever compare Postgres and MySQL for FindMeOn?
No.  I switched to postgres in 2005 and abandoned mysql because of  
too many issues encountered on RoadSound while warehousing data for  
clients.  When FindMeOn split out, it was built in Postgres.
Simply put, at that time mysql could not offer any reasonable  
assurance of data integrity - its remarkable speed advantages came at  
a price.   Meanwhile Postgres was slower, but it valued data  
integrity -- I interpreted that as "Need speed?  Let's cluster".  And  
that worked perfect.  if you wanted data integrity in mysql, you had  
to approach every insert as a unit-test and check it within the  
application logic.  that was ridiculous.

Today, MySql and Postgres are very similar in speed and reliability.   
They finally converged on their goals.
I consider the real differences to be:
	- i flat-out trust postgres more.  mysql did a lot of irresponsible  
things in their product design to make it easier to adapt and gain  
market share.  bugs/deficiencies they touted as features, and  
defaults that are just mindless.
	- postgres pushes people to the ansi sql standard, mysql pushes  
people to mysqlisms.  thats not an issue until you want to redeploy  
on oracle or something else.
	- the postgres query analyzer is far superior.  it gives you *very*  
useful information on how to tweak/rewrite queries and make indexes  
to improve performance.

We're evaluating new systems for FindMeOn right now.  The registered  
user database will stay in postgres, but we do a lot of data  
warehousing for the people search and SNS analytics systems that  
aren't public yet.  postgres has started to outlive its utility on  
those systems, and we're down to 2 finalists for replacement.

> Was Postgres really that much better than MySQL in performance?
It was reliable.  MySQL was not.   that might have changed by now,  
but i won't trust them.

> What tools do you use to create queries, admin the db, etc?
Command line

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy