pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Markus Schaber <schabi@logix-tt.com>
To: pgsql-performance@postgresql.org
Cc: Kumarselvan S <kumar@nexge.com>
Subject: Re: [BUGS] BUG #2567: High IOWAIT
Date: Fri, 11 Aug 2006 10:48:35 +0200
Message-ID: <44DC4463.5@logix-tt.com> (raw)
In-Reply-To: <4D27CB1096EF1C408F4BFAB0046EC7B667D929@ausmailid.aus.pervasive.com>
References: <20060810043408.9C0277E40C2@smtp1.netmagicians.com>
	<4D27CB1096EF1C408F4BFAB0046EC7B667D929@ausmailid.aus.pervasive.com>

Hi, Jim,

Jim Nasby wrote:

> Your biggest win would be to batch those inserts together into
> transactions, if possible.

Using COPY instead of INSERT might even give better wins, and AFAIK some
client libs use COPY internally (e. G. tablewriter from libpqxx).

> If not, the commit_delay settings might help you out.

As far as I understand, this will only help for concurrent inserts by
different clients, dealing throughput for latency. Please correct me if
I'm wrong.

HTH,
Markus
-- 
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org



view thread (4+ messages)

Message-ID: <44DC4463.5@logix-tt.com>
Permalink:  ../44DC4463.5@logix-tt.com/
Also on:    postgresql.org/message-id/44DC4463.5@logix-tt.com

 · 

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: schabi@logix-tt.com, kumar@nexge.com
  Subject: Re: [BUGS] BUG #2567: High IOWAIT
  In-Reply-To: <44DC4463.5@logix-tt.com>

* 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