Re: bad function lets postgres crash

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Clemens Schwaighofer <cs(at)tequila(dot)co(dot)jp>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: bad function lets postgres crash
Date: 2007-07-04 02:07:29
Message-ID: 16686.1183514849@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Clemens Schwaighofer <cs(at)tequila(dot)co(dot)jp> writes:
> both servers are debian packages 8.1.9-1, but on the one that crashed I
> increased the stack depth to 8192. Could it be that postgres ran out of
> memory and terminated itself?

Increasing the stack depth parameter to more than what the kernel really
allows *will* cause crashes, whenever the kernel's limit is exceeded.
Check the ulimit settings the postmaster was started under.

Since (I think) 8.2 we have some code in there that tries to prevent
setting max_stack_depth higher than is safe; but older versions assume
you know what you're doing.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Berend Tober 2007-07-04 04:39:49 Re: How do I aggregate data from multiple rows into a delimited list?
Previous Message Clemens Schwaighofer 2007-07-04 00:36:48 bad function lets postgres crash