| From: | "Jeff Boes" <jboes(at)nexcerpt(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Very long COMMIT times? |
| Date: | 2001-11-12 22:19:20 |
| Message-ID: | 9sphq7$k0h$1@news.tht.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
We've been adjusting the WAL log file count on our database. The only
effects we've seen so far in increasing the count from 8 (default) to 32
(current) are:
1) No more WAL messages in the log 8-/
and 2) very long COMMIT times for some long transactions: I'm talking
about upwards of 10-20 MINUTES to commit after doing hundreds of inserts,
updates and deletes in one transaction. The table involved has some 20K
rows, and is read and updated a few rows at a time by many processes, but
only one (the one doing large numbers of rows) has the lengthy COMMIT
times.
Did this come about because of the increase in WAL count?
--
Jeff Boes vox 616.226.9550
Database Engineer fax 616.349.9076
Nexcerpt, Inc. jboes(at)nexcerpt(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Boes | 2001-11-12 23:00:48 | Re: Very long COMMIT times? |
| Previous Message | Seung Hyun Jeong | 2001-11-12 19:11:35 | about modifying and compiling a component of PostgreSQL |