X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 21C059FB1C4 for ; Fri, 14 Jul 2006 13:25:26 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 40749-07 for ; Fri, 14 Jul 2006 13:25:21 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id A997A9FB1C7 for ; Fri, 14 Jul 2006 13:25:21 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k6EGPDg5022034; Fri, 14 Jul 2006 12:25:13 -0400 (EDT) To: "Craig A. James" cc: pgsql-performance@postgresql.org, sgunderson@bigfoot.com Subject: Re: Kill a session In-reply-to: <44B7B592.1090405@modgraph-usa.com> References: <6BCB9D8A16AC4241919521715F4D8BCEA0FAE8@algol.sollentuna.se> <44B51896.1000808@modgraph-usa.com> <20060712170404.GA27392@uio.no> <44B70017.6000703@modgraph-usa.com> <8780.1152856222@sss.pgh.pa.us> <44B7B592.1090405@modgraph-usa.com> Comments: In-reply-to "Craig A. James" message dated "Fri, 14 Jul 2006 08:17:38 -0700" Date: Fri, 14 Jul 2006 12:25:13 -0400 Message-ID: <22033.1152894313@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/144 X-Sequence-Number: 20004 "Craig A. James" writes: > It's also possible that the INSERT itself is the problem, or adds to the problem. The SIGINT may come after a few million rows have been inserted, so it would have to clean that up, right? No, because we don't use UNDO. The next VACUUM would have a bit of a mess to clean up, but you wouldn't pay for it at the time of the abort. regards, tom lane