pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michal Taborsky <michal@taborsky.cz>
Cc: pgsql-performance@postgresql.org
Subject: Re: Slow INSERT
Date: Tue, 29 Jun 2004 12:02:57 -0400
Message-ID: <1472.1088524977@sss.pgh.pa.us> (raw)
In-Reply-To: <40E18F14.4000600@taborsky.cz>
References: <40E160E6.4080105@taborsky.cz>
	<29095.1088519446@sss.pgh.pa.us>
	<40E1863B.9070208@taborsky.cz>
	<29835.1088522568@sss.pgh.pa.us>
	<40E18F14.4000600@taborsky.cz>

Michal Taborsky <michal@taborsky.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



view thread (8+ messages)  latest in thread

Message-ID: <1472.1088524977@sss.pgh.pa.us>
Permalink:  ../1472.1088524977@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1472.1088524977@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, michal@taborsky.cz
  Subject: Re: Slow INSERT
  In-Reply-To: <1472.1088524977@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox