Re: Hope for a new PostgreSQL era?

From: Chris Travers <chris(dot)travers(at)gmail(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Rodrigo E(dot) De León Plicet <rdeleonp(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Hope for a new PostgreSQL era?
Date: 2011-12-09 00:30:06
Message-ID: CAKt_ZfszcGeiHyG1UapgyMuOFA=efYzu8tEw5tUt5Rwmo0gicA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Dec 8, 2011 at 6:54 AM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:

> There is simply no comparing mysql's backend programming features with
> those of postgres.  Postgres is a development platform in a box, mysql
> is not.
>
This and there are annoyances I have run into with MySQL, such as
deadlocks.... on a system with only one running transaction.... I
traced this problem eventually to multi-row inserts and concluded it
was a race condition in threaded processing. As I say, any db can and
should allow conflicting transactions to deadlock. It takes special
talent to allow transactions to deadlock against *themselves*......

Interestingly I have customers who run both MySQL and PostgreSQL and
have had similar issues with transactions deadlocking against
themselves on MySQL, so I know I am not unique here.

MySQL, I am sorry to say, is not catching up to PostgreSQL at least
from where I stand except for the few very specific workloads that its
query cache are designed to work with.

Best Wishes,
Chris Travers

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Chris Travers 2011-12-09 00:34:49 Re: Hope for a new PostgreSQL era?
Previous Message Rodger Donaldson 2011-12-09 00:09:34 Re: Hope for a new PostgreSQL era?