| From: | John DeSoi <desoi(at)pgedit(dot)com> |
|---|---|
| To: | PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | drupal.org MySQL database issues |
| Date: | 2007-05-16 05:34:32 |
| Message-ID: | A4881DB1-4A27-482A-8408-4F89D2867C0D@pgedit.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
Maybe they could be convinced to use the "other" database supported
by Drupal :).
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.
John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Kahwe Smith | 2007-05-16 09:49:18 | Re: drupal.org MySQL database issues |
| Previous Message | Jim C. Nasby | 2007-05-16 01:30:32 | Re: 2nd annual State of Lightning Talks at OSCON |