News for hackers. Stuff that matters.
Re:Ingesting MySQL data at scale – Part 1 by spudlyo on Friday August 12, 2016 @01:44AM (#12273589)
Sadly at present Postgres has absolutely awful mysqldump support (It's not even on their roadmap) so I doubt it would be a good fit for Pinterest's environment.
Re:Ingesting MySQL data at scale – Part 1 by dijit on Friday August 12, 2016 @05:10AM (#12274217)
is that a joke?

of course they wont support mysqldump, but there is pg_dump, which does the same sort of thing except you can dump to binary and compress it on the way without pipes/forks.

Re:Ingesting MySQL data at scale – Part 1 by spudlyo on Friday August 12, 2016 @09:01AM (#12275227)
Wait, hold the phone, are you telling me by migrating to Postgres I can shave a handful of system calls off my long-running i/o bound logical backups!? Oh Postgres, is there anything you can't do better than MySQL?
Re:Ingesting MySQL data at scale – Part 1 by dijit on Friday August 12, 2016 @10:50AM (#12276147)
No I'm telling you that `mysqldump` will not support postgres the same way that a diesel truck will not take petrol.
[dead]
Re:Ingesting MySQL data at scale – Part 1 by dreaminvm on Friday August 12, 2016 @04:40PM (#12278644)
Not sure if you are trolling, but why would Postgres want to support mysqldump? Postgres has pg_dump and MySQL has mysqldump. If you are comparing the capabilities of pg_dump vs mysqldump, that's a different discussion.