Re: drupal.org MySQL database issues

From: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: John DeSoi <desoi(at)pgedit(dot)com>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: drupal.org MySQL database issues
Date: 2007-05-16 16:44:25
Message-ID: 20070516164425.GS14548@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On Wed, May 16, 2007 at 09:42:36AM -0700, Joshua D. Drake wrote:
> Jim C. Nasby wrote:
> >On Wed, May 16, 2007 at 09:26:45AM -0700, Joshua D. Drake wrote:
> >>John DeSoi wrote:
> >>>Maybe they could be convinced to use the "other" database supported by
> >>>Drupal :).
> >>>
> >>>
> >>>http://drupal.org/node/144228
> >>>
> >>>What's the deal?
> >>As someone who has made a ton of money making Drupal work with
> >>PostgreSQL, I would note that Durpal is not fast on PostgreSQL out of
> >>the box. It needs help to get there.
> >>
> >>I don't know that they would be happy unless they had someone with Pg
> >>experience helping them.
> >
> >Is it the drupal code itself that's the issue or just a matter of tuning
> >PostgreSQL?
>
> Both. Obviously tuning postgresql is a big part but they have some odd
> query issues to deal with. And if they have *any* custom modules, oh boy.

Well, while they're in pain it sounds like a good time to get them
thinking about changing preferred databases as well as cleaning up some
of the code... I'm sure that if their preferred database was PostgreSQL
you'd be seeing more work. :)
--
Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Joshua D. Drake 2007-05-16 16:51:20 Re: drupal.org MySQL database issues
Previous Message Joshua D. Drake 2007-05-16 16:43:32 Re: drupal.org MySQL database issues