Re: Solved? Re: 8.2.4 signal 11 with large transaction

From: Andrew - Supernews <andrew+nonews(at)supernews(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Solved? Re: 8.2.4 signal 11 with large transaction
Date: 2007-07-21 01:02:20
Message-ID: slrnfa2mor.31cl.andrew+nonews@atlantis.supernews.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On 2007-07-20, Bill Moran <wmoran(at)collaborativefusion(dot)com> wrote:
> It just occurred to me that there's another wildcard in this one.
> The 8.1 system I tested was on FreeBSD 5.5, while both 8.2 systems
> were running on FreeBSD 6.2. I wonder if FreeBSD has changed
> which signal gets sent on memory exhaustion?

Neither 5.x nor 6.x send any sort of signal simply because maxdsize was
reached; the only effect of reaching maxdsize is that further memory
allocations fail.

I'd guess that the most likely cause for a sig11 under those circumstances
is a stack overflow resulting from recursive errors...

--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Hiroshi Saito 2007-07-21 01:18:27 Re: psql-odbc configure error
Previous Message Jeff Davis 2007-07-21 00:37:42 Re: Foreign key constraint question

Browse pgsql-hackers by date

  From Date Subject
Next Message ohp 2007-07-21 07:40:31 Re: Backend memory growing too much
Previous Message Jim C. Nasby 2007-07-20 21:01:29 Re: CREATE TABLE LIKE INCLUDING INDEXES support