| From: | Lukas Kahwe Smith <smith(at)pooteeweet(dot)org> |
|---|---|
| To: | John DeSoi <desoi(at)pgedit(dot)com> |
| Subject: | Re: drupal.org MySQL database issues |
| Date: | 2007-05-16 09:49:18 |
| Message-ID: | 464AD39E.2040402@pooteeweet.org |
| 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?
>
> 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.
Also by moving from MyISAM to InnoDB, they not only get row level
locking, they also get MVCC ..
regards,
Lukas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonah H. Harris | 2007-05-16 13:05:56 | Re: drupal.org MySQL database issues |
| Previous Message | John DeSoi | 2007-05-16 05:34:32 | drupal.org MySQL database issues |