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 TAA73850 for ; Mon, 3 May 1999 19:58:50 -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 TAA28436; Mon, 3 May 1999 19:57:46 -0400 (EDT) To: rgireyev@cnmnetwork.com cc: pgsql-sql@hub.org Subject: Re: [SQL] Slow Inserts Again In-reply-to: Your message of Mon, 3 May 1999 15:00:19 -0700 <199905032159.RAA58721@hub.org> Date: Mon, 03 May 1999 19:57:46 -0400 Message-ID: <28434.925775866@sss.pgh.pa.us> From: Tom Lane "Rudy Gireyev" writes: > Is it at all possible that the optimizer is responsible for this behaviour? Not in the sense that it might be choosing a bad plan --- there is only one way to insert a tuple ;-). Size of the table doesn't matter. If the problem is indeed some kind of memory leak, the optimizer is as likely a place for the leak as any other, I suppose. regards, tom lane