Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA11881 for ; Mon, 3 May 1999 12:21:58 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id MAA20460; Mon, 3 May 1999 12:19:56 -0400 (EDT) From: Bruce Momjian Message-Id: <199905031619.MAA20460@candle.pha.pa.us> Subject: Re: [SQL] Slow Inserts Again In-Reply-To: <19916.925742572@sss.pgh.pa.us> from Tom Lane at "May 3, 1999 10:42:52 am" To: Tom Lane Date: Mon, 3 May 1999 12:19:56 -0400 (EDT) CC: Frank Morton , Vadim Mikheev , pgsql-sql@hub.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > >> 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. Yes, memory use it the place to look. We have had bugs in the past that did not free memory, causing this problem. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026