DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:mime-version:content-type
	:x-google-sender-auth;
	b=XGBDV91KlwvkY4T2Hs1BCUhZTE24sNS2l82TmmaxWdTDLDfclwLZzJ6nEPcNI8PnFc
	LRdfysAMlcnaKmNBiIl61wl72F4HI+9aGdBK7VY8xwU9VLLWRs/iYD/Y/v5FrM87I5Pn
	cxX2IwIorpzHZVR/EBHhR4Ezj/ZCS5BTNUUmg=
Message-ID: <1775c5ea0808231747m71c4e75fn9b5c45ed604edfe8@mail.gmail.com>
Date: Sun, 24 Aug 2008 01:47:36 +0100
From: "Loic Petit" <tls.wydd@free.fr>
To: scott.marlowe@gmail.com
Subject: Re: Large number of tables slow insert
Cc: max@nts.biz.ua, pgsql-performance@postgresql.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_94019_27950537.1219538856698"

------=_Part_94019_27950537.1219538856698
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I was a bit confused about the read and write sorry ! I understand what you
mean...
But do you think that the IO cost (of only one page) needed to handle the
index writing is superior than 300ms ? Because each insert in any of these
tables is that slow.
NB: between my "small" and my "big" tests the only difference is the number
of table (10 and 3000), there is almost the same amount of on-disk data

------=_Part_94019_27950537.1219538856698
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">I was a bit confused about the read and write sorry ! I understand what you mean...<br>But do you think that the IO cost (of only one page) needed to handle the index writing is superior than 300ms ? Because each insert in any of these tables is that slow.<br>
NB: between my &quot;small&quot; and my &quot;big&quot; tests the only difference is the number of table (10 and 3000), there is almost the same amount of on-disk data<br></div>

------=_Part_94019_27950537.1219538856698--