Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA97774 for ; Mon, 3 May 1999 10:44:37 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA19918; Mon, 3 May 1999 10:42:52 -0400 (EDT) To: "Frank Morton" cc: "Vadim Mikheev" , pgsql-sql@hub.org Subject: Re: [SQL] Slow Inserts Again In-reply-to: Your message of Mon, 3 May 1999 08:50:21 -0500 <06c001be956b$e35db0c0$8355e5ce@base2inc.com> Date: Mon, 03 May 1999 10:42:52 -0400 Message-ID: <19916.925742572@sss.pgh.pa.us> From: Tom Lane >> Why _each_? >> Enclose ALL statements by begin; & end; to insert ALL data >> in SINGLE transaction: But the transaction boundaries wouldn't have anything to do with Frank's real problem, which is that the insertions are getting slower and slower. There's no good reason for that; and other people are not reporting any comparable problems. (Considering that we *have* been getting trouble reports for more-than-2-gig tables, it's clear that people are putting large amounts of data into 6.5; so it's not like Frank is stressing the system more than it has been before.) Frank, what does the memory usage of the backend that's processing this insertion look like; has it been growing steadily? I'm wondering whether you could have a problem with poor malloc behavior, or some such. regards, tom lane