From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | John DeSoi <desoi(at)pgedit(dot)com> |
Cc: | PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: drupal.org MySQL database issues |
Date: | 2007-05-16 16:26:45 |
Message-ID: | 464B30C5.8030004@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
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.
Joshua D. Drake
>
> The root of the problem that our database server is overloaded. This is
> causing table locks:
>
> Table locking is also disadvantageous under the following scenario:
> * A client issues a SELECT that takes a long time to run.
> * Another client then issues an UPDATE on the same table.
> This client waits until the SELECT is finished.
> * Another client issues another SELECT statement on the same
> table. Because UPDATE has higher priority than SELECT, this
> SELECT waits for the UPDATE to finish, and for the first
> SELECT to finish.
>
>
>
>
> John DeSoi, Ph.D.
> http://pgedit.com/
> Power Tools for PostgreSQL
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2007-05-16 16:36:45 | Re: drupal.org MySQL database issues |
Previous Message | Leif B. Kristensen | 2007-05-16 13:56:51 | Re: drupal.org MySQL database issues |