From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
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:42:36 |
Message-ID: | 464B347C.3020500@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
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.
Joshua D. Drake
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2007-05-16 16:43:32 | Re: drupal.org MySQL database issues |
Previous Message | Jim C. Nasby | 2007-05-16 16:36:45 | Re: drupal.org MySQL database issues |