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 669CF536E5 for ; Sat, 23 Apr 2005 16:51:06 -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 72785-04 for ; Sat, 23 Apr 2005 19:50:56 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 3D475536E1 for ; Sat, 23 Apr 2005 16:50:55 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j3NJouUT014611; Sat, 23 Apr 2005 15:50:56 -0400 (EDT) To: Richard Plotkin Cc: pgsql-performance@postgresql.org Subject: Re: Disk filling, CPU filling, renegade inserts and deletes? In-reply-to: <31935aa56e9539c5648cb09e78152c03@richardplotkin.com> References: <6f4567d4e64297b356e2d71ec392cdae@richardplotkin.com> <4574.1114030270@sss.pgh.pa.us> <9c5b2bf6a0f5a0bc0abeb6b6c5cf7973@richardplotkin.com> <2a9467bc6e6dab5d997427c4ef6158e3@richardplotkin.com> <12016.1114279585@sss.pgh.pa.us> <12135.1114280225@sss.pgh.pa.us> <31935aa56e9539c5648cb09e78152c03@richardplotkin.com> Comments: In-reply-to Richard Plotkin message dated "Sat, 23 Apr 2005 11:37:30 -0700" Date: Sat, 23 Apr 2005 15:50:56 -0400 Message-ID: <14610.1114285856@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/654 X-Sequence-Number: 12051 Richard Plotkin writes: > Thanks for your responses this morning. I did the select relname, and > it returned 0 rows. I do have one function that creates a temp table > and fills it within the same transaction. I'm pasting it below. > Perhaps the "ON COMMIT DROP" is causing problems, and I need to drop > the table at the end of the function instead of using ON COMMIT DROP? Well, I think we can conclude that the function is pushing way more data into the temp table than you expect. I am wondering if that loop in the middle of the function is turning into an infinite loop --- could it be finding some sort of cycle in your page data? You might want to add some RAISE NOTICE commands to the loop so you can track what it's doing. regards, tom lane