X-Original-To: pgsql-performance@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 4553C4762EF for ; Sat, 12 Apr 2003 16:53:43 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 886334762E1 for ; Sat, 12 Apr 2003 16:53:42 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h3CKrN2L019652; Sat, 12 Apr 2003 16:53:23 -0400 (EDT) To: shane hill Cc: pgsql-performance Subject: Re: update query blows out In-reply-to: <3E98579F.8040904@adobe.com> References: <564664787.20030410102049@procedium.com> <3E98498C.80306@adobe.com> <18800.1050167784@sss.pgh.pa.us> <3E98579F.8040904@adobe.com> Comments: In-reply-to shane hill message dated "Sat, 12 Apr 2003 11:14:55 -0700" Date: Sat, 12 Apr 2003 16:53:23 -0400 Message-ID: <19651.1050180803@sss.pgh.pa.us> From: Tom Lane X-Spam-Status: No, hits=-32.3 required=5.0 tests=BAYES_00,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200304/127 X-Sequence-Number: 1633 shane hill writes: > I am having a problem with an update transaction. I need to update 4000+ > records but the update query keeps blowing out postgres and at times I > am forced to restart the postmaster or reboot my server if I update > 2500+ records. The query is fine with 2225 records it is just somewhere > beyond 2225 that brings the server down. > [ core dump in heavily-recursive routine ] I think you are running into a stack-size problem. A quick look at "ulimit -a" on my own OS X machine shows that the default stack limit is a mere 512KB, which is verging on the ridiculously small :-(. Try setting "ulimit -s 10000" or so in the script that launches the postmaster. Now that I look at it, the -d setting is on the miserly side as well ... regards, tom lane