Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id 6DD59B5DC27
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Wed, 19 Oct 2011 15:55:42 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 60483-02
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Wed, 19 Oct 2011 18:55:36 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0-rc2
Received: from sam.nabble.com (sam.nabble.com [216.139.236.26])
	by mail.postgresql.org (Postfix) with ESMTP id 138CCB5DC1E
	for <pgsql-performance@postgresql.org>;
	Wed, 19 Oct 2011 15:55:35 -0300 (ADT)
Received: from [192.168.236.26] (helo=sam.nabble.com)
	by sam.nabble.com with esmtp (Exim 4.72)
	(envelope-from <kzsoltkzsolt@freemail.hu>) id 1RGbId-00038s-0K
	for pgsql-performance@postgresql.org; Wed, 19 Oct 2011 11:55:35 -0700
Date: Wed, 19 Oct 2011 11:55:35 -0700 (PDT)
From: kzsolt <kzsoltkzsolt@freemail.hu>
To: pgsql-performance@postgresql.org
Message-ID: <1319050535000-4919006.post@n5.nabble.com>
In-Reply-To: <4E9E204B.2040608@ringerc.id.au>
References: <1318939765661-4913425.post@n5.nabble.com>
	<4E9E204B.2040608@ringerc.id.au>
Subject: Re: Heavy contgnous load
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-0.767 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, T_TO_NO_BRKTS_FREEMAIL=0.01,
	URI_HEX=1.122
X-Spam-Level: 
X-Archive-Number: 201110/169
X-Sequence-Number: 45391

"try to have as few indexes as possible and do your inserts inside
transactions in batches, rather than one-by-one as individual statements. "
That is the main problem. I use now few index as possible. Unfortunately the
one-by-one INSERT is nature of or system. To join (batch) inserts is require
spacial cache with inactivity timeout. But this timout are make more trouble
for our application. The flat file has same problem. 

--
View this message in context: http://postgresql.1045698.n5.nabble.com/Heavy-contgnous-load-tp4913425p4919006.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.