public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] PostgreSQL Vs MySQL @Uber
Date: Sat, 30 Jul 2016 00:01:09 +0100	[thread overview]
Message-ID: <6189756.X50q7HfFPC@dell_xps> (raw)
In-Reply-To: <CAGfcS_ndFLXw+rB2rmewiVwwG2rO5JQFt5-Hw7Y-Hrat1jZUXQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]

On Saturday 30 Jul 2016 06:38:01 Rich Freeman wrote:
> On Sat, Jul 30, 2016 at 6:24 AM, Alan McKinnon <alan.mckinnon@gmail.com> 
wrote:
> > On 29/07/2016 22:58, Mick wrote:
> >> Interesting article explaining why Uber are moving away from PostgreSQL.
> >> I am
> >> running both DBs on different desktop PCs for akonadi and I'm also
> >> running
> >> MySQL on a number of websites.  Let's which one goes sideways first.  :p
> >> 
> >>  https://eng.uber.com/mysql-migration/
> > 
> > I don't think your akonadi and some web sites compares in any way to Uber
> > and what they do.
> > 
> > FWIW, my Dev colleagues support and entire large corporate ISP's
> > operational and customer data on PostgreSQL-9.3. With clustering. With no
> > db-related issues :-)
> 
> Agree, you'd need to be fairly large-scale to have their issues, but I
> think the article was something anybody interested in databases should
> read.  If nothing else it is a really easy to follow explanation of
> the underlying architectures.
> 
> I'll probably post this to my LUG mailing list.  I think one of the
> Postgres devs lurks there so I'm curious to his impressions.
> 
> I was a bit surprised to hear about the data corruption bug.  I've
> always considered Postgres to have a better reputation for data
> integrity.  

Yes, same here, I would be interested to hear what the Postgres dev says, 
should he respond to it.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-07-29 23:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29 20:58 [gentoo-user] PostgreSQL Vs MySQL @Uber Mick
2016-07-29 22:24 ` Alan McKinnon
2016-07-29 22:38   ` Rich Freeman
2016-07-29 23:01     ` Mick [this message]
2016-08-01  1:48       ` Douglas J Hunley
2016-08-01  7:16     ` J. Roeleveld
2016-08-01 13:43       ` james
2016-08-01 16:49         ` J. Roeleveld
2016-08-01 18:03           ` Rich Freeman
2016-08-02  5:51             ` james
2016-08-11 12:48               ` Douglas J Hunley
2016-08-12 13:00                 ` james
2016-08-12 14:13                   ` R0b0t1
2016-08-12 14:15                     ` R0b0t1
2016-08-12 18:01                       ` james
2016-08-02  5:16           ` james
2016-08-04 10:09             ` J. Roeleveld
2016-08-04 17:08               ` james
2016-08-04 19:19                 ` R0b0t1
2016-08-11 12:43         ` Douglas J Hunley
2016-08-01 15:01       ` Rich Freeman
2016-08-01 17:31         ` J. Roeleveld
2016-08-02  1:07           ` Rich Freeman
2016-08-02  7:03             ` J. Roeleveld
2016-08-01 23:18         ` Alan McKinnon
2016-08-02  0:55           ` Rich Freeman
2016-08-02 17:49 ` Rich Freeman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6189756.X50q7HfFPC@dell_xps \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox