| From: | "Jeff Boes" <jboes(at)nexcerpt(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Poor performance of UPDATE against busy table |
| Date: | 2001-09-06 18:31:51 |
| Message-ID: | 9n8fcr$2oqo$1@news.tht.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
We have a table being used as a job queue. There's one 'scheduler'
process that manipulates jobs (inserting, updating, and deleting rows/jobs as
they change status). There are a number (~24) of processes reading and
updating rows as they 'claim' and 'complete' jobs.
Our problem is that throughput on this table is fairly low. Updates by
the 'scheduler' sometimes take 15 seconds (!!). We've tried various
combinations of LOCK TABLE commands, but without much success.
Does anyone know if there are ways to improve the performance of UPDATE
against a table where there are many readers?
--
Jeff Boes vox 616.226.9550
Database Engineer fax 616.349.9076
Nexcerpt, Inc. jboes(at)nexcerpt(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ross J. Reedstrom | 2001-09-06 19:15:22 | Re: Poor performance of UPDATE against busy table |
| Previous Message | Tom Lane | 2001-09-06 16:56:31 | Re: Need help or advices : databases and tables invisibles and not accessibles ! |