| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michal Taborsky <michal(at)taborsky(dot)cz> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Slow INSERT |
| Date: | 2004-06-29 16:02:57 |
| Message-ID: | 1472.1088524977@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Michal Taborsky <michal(at)taborsky(dot)cz> writes:
> I've read the discussion in "Trying to minimize the impact of
> checkpoints" thread and I get it, that there is nothing I can do about
> it. Well, we'll have to live with that, at least until 7.5.
You could experiment with the checkpoint interval (checkpoint_timeout).
A shorter interval will mean more total I/O (the same page will get
written out more often) but it should reduce the amount of I/O done by
any one checkpoint. You might find that the extra overhead is worth it
to reduce the spikes.
But 7.5 should provide a much better answer, yes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin M. Roy | 2004-06-29 16:03:24 | Re: postgres 7.4 at 100% |
| Previous Message | eleven | 2004-06-29 15:55:37 | High load average with PostgreSQL 7.4.2 on debian/ibm eserver. |