From: Tom Lane <tgl@sss.pgh.pa.us>
To: shane hill <shill@adobe.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: update query blows out
Date: Sat, 12 Apr 2003 16:53:23 -0400
Message-ID: <19651.1050180803@sss.pgh.pa.us> (raw)
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>
shane hill <shill@adobe.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, shill@adobe.com
Subject: Re: update query blows out
In-Reply-To: <19651.1050180803@sss.pgh.pa.us>
References: <564664787.20030410102049@procedium.com> <3E98498C.80306@adobe.com> <18800.1050167784@sss.pgh.pa.us> <3E98579F.8040904@adobe.com> <19651.1050180803@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox