X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 99072D1B1A5 for ; Tue, 29 Jun 2004 12:47:38 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 45343-08 for ; Tue, 29 Jun 2004 15:47:37 +0000 (GMT) Received: from mx.mall.cz (mx.mall.cz [81.30.232.20]) by svr1.postgresql.org (Postfix) with ESMTP id 7D432D1B19F for ; Tue, 29 Jun 2004 12:47:35 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by mx.mall.cz (Postfix) with ESMTP id D3EDC4814A; Tue, 29 Jun 2004 17:47:34 +0200 (CEST) Received: from mx.mall.cz ([127.0.0.1]) by localhost (posta [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06924-07; Tue, 29 Jun 2004 17:47:27 +0200 (CEST) Message-ID: <40E18F14.4000600@taborsky.cz> Date: Tue, 29 Jun 2004 17:47:32 +0200 From: Michal Taborsky User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-performance@postgresql.org Subject: Re: Slow INSERT References: <40E160E6.4080105@taborsky.cz> <29095.1088519446@sss.pgh.pa.us> <40E1863B.9070208@taborsky.cz> <29835.1088522568@sss.pgh.pa.us> In-Reply-To: <29835.1088522568@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/300 X-Sequence-Number: 7358 Tom Lane wrote: > Actually, the simpler theory is that the slowdown is caused by > background checkpoint operations. Now a checkpoint would slow > *everything* down not only this one insert, so maybe that's not > the right answer either, but it's my next idea. You could check > this to some extent by manually issuing a CHECKPOINT command and > seeing if you get an insert hiccup. Note though that closely > spaced checkpoints will have less effect, because less I/O will > be triggered when not much has changed since the last one. So > you'd want to wait a bit between experiments. Aha! This is really the case. I've let the test run and issued manual CHECKPOINT command. The command itself took about 3 secs and during that time I had some slow INSERTS. So we know the reason. 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. Thanks of the help all the same. -- Michal Taborsky http://www.taborsky.cz