Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 4267147590F for ; Fri, 26 Apr 2002 18:54:25 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g3QMsQF12721; Fri, 26 Apr 2002 18:54:26 -0400 (EDT) To: "Josh Berkus" Cc: pgsql-sql@postgresql.org Subject: Re: Function won't complete In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Fri, 26 Apr 2002 14:57:20 -0700" Date: Fri, 26 Apr 2002 18:54:26 -0400 Message-ID: <12718.1019861666@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200204/341 X-Sequence-Number: 7605 "Josh Berkus" writes: > I am currently testing a massive data update function, which takes a > large amount of raw data (in 3 tables comprising over 2 million records > total) and organizes and cleans that data in a series of successive > steps for the final relational database. > The problem is, it doesn't complete. About 1/3 of the way in to the > data updates, postgres gets stuck in an endless cycle of recycling > transaction logs and child processes and won't finish (current longest > abort time is 37 minutes). You sure it's not just a programming error (the proverbial unconstrained join, for example)? Without seeing the query(s) I doubt we can help you much. regards, tom lane